Redmine

This feature is very high on our wish list as well. Specifically it would be nice to be able to use categories in a sub project that are defined in the parent project.
We work with a long running project and we create weekly builds. Each weekly build is managed in a sub project, and it's rather tedious to recreate the categories for every sub project. being able to create them once in the parent project (or indeed globally) would be much more convenient.

+1. We are using maybe roughly 20 categories, they are really a pain to input in each project.

+1: it is necessary

Me too!!! - Seems to be a duplicate of #2521

+1
Bump - this feature is really important to me, too...

+1

+1

Does this already have a target version?

+1

+100 for this

+1
This would save so much time! we have new projects entered weekly. Updating the categories when they are the same for each project is very time consuming.

I would like to work on this. Is it okay to use the existing issue_categories table with project_id set to 0 for the global categories? Or is there a better approach?

+1

Really frustrating to write same issues all over again for different projects.

+1

+1

+1 Bump!!

I wish this feature.

+1

Me too!

+1 ! Would be so helpful !

Honestly I was confused and shocked to find that the default was not "superprojects can filter on all subprojects' categories"; I don't even understand a data model where that's not obviously true. Please consider this; the usage as it stands is just weird for subprojects (the category appears in issue lists but cannot be used as a search filter....guh..?...)

I was so happy when I found the issue categories. They are perfect to mark issues for meetings. But today, when I tried to filter for my categories, I had to find out, that you cannot filter over several projects. I guess my understanding of using issue categories are totally different from the programmer's.

The filter should search for the tag name in subprojects and not the tag id. With this method, you could make global categories by adding the same category to every project.

Dan Mick, I feel with you.

+1

+1

As a workaround, you can use a script in your favorite scripting language which creates the issue categories as requested using the REST API. I'm currently doing this because I also missed a feature like default categories for all projects.

I completely agree, this would be a great feature!

+1

+1

+1

Thanks for the tips TJ.
However this workaround does not allow automatic assignment of tickets depending of the category.

+1 with the global (default) categories (or with the sharing with subprojects - see #5358)!