[PROJECT] Issues should have Categories
Redmine provides Categories:
Some Example Categories for wt
Project (Issues subjecting the project resources and processes)
It's not so good if there are too many categories, usually it's dictated by the amount of issues filed (e.g. only when one widget gets many issues filed, then it gets an own category)
Updated by I. Lazaridis over 8 years ago
Is there any reason why you don't even comment to this issue?
Such "Categories" are really a very basic organizational construct, found in nearly every open-source project.
And it needs really just a few minutes to implement. An additional benefit is that you can (optionally) assign issues automatically to project members.
Issue categories Issue categories let you to organize issues. Categories can for example correspond to the different components of your project. You are able to configure your own set of issue categories for each individual project. It is also possible to auto-assign new issues to a specific user based on the chosen category of the newly created issues. The following properties are configurable for (each of the) issue categories: Name: The text you want to be displayed to identify the issue category. This field is required. Assigned to: The project member to who you want to auto-assign newly created issues in this category. This field is optional.