[#JRA-4505] Assign schemes at the Project category level

JIRA

Assign schemes at the Project category level

Created: 08/Sep/04 06:07 AM Updated: 29/Jun/08 06:25 PM

Component/s:

Project Management

Affects Version/s:

3.0 Enterprise Preview

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-15170~~ Per-module configuration

~~JRA-12690~~ I would like it if all configurations, e.g. screens, schemes, custom fields, etc. could be set up on a Category Basis.

Part

This issue is incorporated by:

JRA-7020 Allow support for project schemes or templates

Participants:	Andrew Hammond, Brian Riedinger, Dave Dixon, Mark Michaelis, Niall Stapley and Robert Castaneda
Since last comment:	22 weeks, 3 days ago
Labels:

Description

« Hide

It would make life easier if we could assign the following at the Project Category level and then override at the Project level:

Notification Scheme:
Permission Scheme:
Issue Security Scheme:
Workflow Scheme:

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robert Castaneda added a comment - 08/Sep/04 06:14 AM

CVS repositories should also be added

[ Permlink | « Hide ]

Andrew Hammond added a comment - 14/Mar/06 04:25 AM

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...

[ Permlink | « Hide ]

Mark Michaelis added a comment - 10/May/06 02:05 AM

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...

[ Permlink | « Hide ]

Dave Dixon added a comment - 06/Apr/07 05:29 PM

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.

[ Permlink | « Hide ]

Brian Riedinger added a comment - 24/Dec/07 02:41 PM

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.

[ Permlink | « Hide ]

Niall Stapley added a comment - 08/May/08 03:38 AM

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.