Feature #9306

Per-tracker issue categories

Added by Lars Erik Gullerud about 6 years ago. Updated over 1 year ago.

Status:NewStart date:2011-09-22
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

It would be very useful when defining categories inside a Project if one could select what trackers this category is valid for (similar to the way one selects what trackers are used in a Project).

Case example:

For our "feature" tracker we only need 3 categories, each assigned to one of three users who will follow up the feature request and do a design for that area. However for "bugs" tracker there are a lot more categories as these are assigned to individual engineers responsible for a given area. Having to see (and be able to select!) all these categories in the "feature" tracker makes our users submit a lot of requests that end up in the wrong place.

Of course we could split every single project into sub-projects and have only one tracker (and one set of categories) in each sub-project, however this is a less than optimal workaround...


Related issues

Duplicated by Redmine - Feature #23747: Per-tracker Issue Categories Closed

History

#1 Updated by Etienne Massip about 6 years ago

  • Assignee deleted (Jean-Philippe Lang)

#2 Updated by Samuel F. Baggen over 4 years ago

categories ? mmmh...

I was thinking on a similar/same need, for example, if you do a change that a customer needs to beta-test, think about hardware-specific customers

We could have a system like tags, for example to send notifications to the customers that has X-tagged specific hardware to betatest the new change

#3 Updated by Luiz Moura over 1 year ago

+1

It could be made as the plugin below

https://github.com/nanego/redmine_per_tracker_categories

This is very useful, do not know why redmine does not have this feature.

#4 Updated by Toshi MARUYAMA over 1 year ago

Also available in: Atom PDF