In 2015 "This suggestion is a priority for the JIRA development team"

8 years later it is still not implemented.

If the SLA for a "priority" issue is > 8 years, that certainly explains the11,000+ issues in their backlog.

Can't begin to say how grateful we would be for this feature....

We need a solution for those times when there's 500+ projects to update.

You know what could be ideal and cover the concerns people have mentioned? A checkbox interface, e.g. I can select Category X and then I can check 'select all' but still uncheck any 'special' projects which should not be updated.

Else, Jason Kemp's idea to make "a new "Project Scheme" setting that encapsulates all the other settings schemes into one setting to change" was also very interesting and possibly more flexible.

We'll take anything that makes this less painful, especially if there's an API to call it with

Nice to have, we're missing this feature

It would be very helpfull 

Having dealt with this for a long time, I've come to the conclusion that the existing Project Category, specifically, shouldn't be used for this feature. We currently use Project Category for roughly division/department groups with multiple projects which aren't always the same as the project settings.

What there should be is a new "Project Scheme" setting that encapsulates all the other settings schemes into one setting to change.

We are running Jira server instance with over 300 projects and > 1600 users.

It would be much easier to maintain and administer Jira if we could associate Workflow Schemes/Permission Scheme/Issue Security Scheme with Categories.

We were just discussing this issue again today. We use project category to indicate (among other things) shared configurations, We will be moving a team to a different project category next month, which means a lot of manual effort to add that project to various field configurations, update project schemes, etc.

It would be AMAZING if we could just change the category, which would then step us through a project migration process, especially if it could include field configuration, e.g. "Field X is not valid for Category Y. Would you like to add it?" "Oh heck yes!" (click) "Done."

Please do this for SERVER, not only DC

PLEASE DO THIS

The possibility to assign user/group permissions to a project category would be a huge advatage for our company. We have many different department on aour Jira. Its allways trouble to get the right permissions for every team and project.

I vote to assign a user/group(s) permission to a project category, would be a major advantage for our organization too! 

I have a number of projects and want to use project category to define the programmes used.

This would allow me to identify and report on which programmes are reporting a high level of issues, hence feedback to the vendor we are using. 

Now using Power BI to provide reports based upon Project Category via JIRA 

+1

It would be nice if it could be used during Creation to set up a new Project in the same way as other Projects in the category.

+1

It would be handy to be able to assign permissions to project categories, allowing only certain groups from seeing certain projects.

As the number of projects grow in an instance of JIRA something like this would prevent users from getting bogged down in projects they have no relation too.

So the ability to assign a group(s) to a project category would be a major adventage in my book.

This feature would help us enormously.
We need to prevent users from different departments from viewing projects from other departments and setting permissions in each project separately is a significant amount of work (we're currently running 50+ projects simultaneously).

This would make life much simpler when you have to manage lots of users and lots of projects at the same time.

A Global Component Scheme would vastly cut down system maintenance time when creating new projects using the same components. At the project level, it would need the capability to override both the assigned "component lead" & "default assignee" per component.

Finally, there should be a bulk feature to quickly re-assign all component leads from a particular user (terminated employee) to another user for employee turn-over for all projects (both global level and project level). This would literally save hours of system admin maintenance time.

Global Component Scheme Features Desired / Benefits:

1. Quickly add global component scheme (multiple schemes to choose from) to new projects
2. Set global component leads in one step
3. Component lead & default assignee (project lead, component lead, or unassigned) can be overridden at project level
4. Ensure consistent naming (for filters, dashboards, & reports)
5. Additional feature to re-assign all component leads for a terminated employee with a replacement lead across all projects in one step (when deactivating the user)

We'd love this too. Our project management overhead would be greatly reduced by this.

Yes, we have 51 projects and growing, making managing per individual project harder and more error prone.

Our development teams "complete" projects then they start new ones and maintain the old ones. We put all the projects into categories, some are internal only and some for disparate sets of clients. It would be nice to allocate the various "schemes" for user groups to project categories. It would also be nice for a team to have its own category too, and allow access to certain sets of projects based on the viewer's "category" permissions.

This feature should also be applied to Components. I would like to apply different fields and workflow steps to the issues in my project based on the component that is affected. For example, a UI issue goes through a different set of peer reviews than a Database issue.

It seems that the Project layer is too high to declare workflows, etc.

This would be a fantastic feature. Way too much of my time in JIRA is spent assigning the same workflow, permission, or notification scheme to a slew of projects, all of which belong to the same project category.

To take it a step further, I'd love to see JIRA eventually move to an n-level project hierarchy, so schemes could be assigned at a top-level project, and overridden by lower-level projects when necessary.

We also need especially the "per Project (Category)" Permission Scheme as the projects want to adjust the assignable users. And I think it would be even better, if there is some kind of inheritance:

Global Level - Project Category Level - Project Level

Thus, if Project does not override e. g. the "Assignable User" it is taken from "Project Category Level" and so on...

This would be a great feature

We also have a need for this, we have 27 projects in 7 categories and for the most part all of the projects in the category have the same workflow, permission etc, so when it comes to updating workflows for even minor changes having to do the change in 10 projects is not fun...

CVS repositories should also be added