-
Suggestion
-
Resolution: Unresolved
-
None
-
8
-
7
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
This suggestion is a priority for the JIRA development team, but I am not able to provide an accurate estimate for when this will be resolved. We will update this issue as soon as we can confidently project a release.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
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:
- duplicates
-
JRASERVER-2937 Category permission schemes
- Closed
-
JRASERVER-45621 Project-level Notification Scheme
- Closed
- is duplicated by
-
JRASERVER-12690 I would like it if all configurations, e.g. screens, schemes, custom fields, etc. could be set up on a Category Basis.
- Closed
-
JRASERVER-15170 Per-module configuration
- Closed
- is incorporated by
-
JRASERVER-67231 Allow support for project schemes or templates
- Closed
-
JRASERVER-7020 Allow support for project schemes or templates
- Future Consideration
- relates to
-
JRACLOUD-4505 Assign schemes at the Project category level
- Closed
-
JRASERVER-28833 Project bulk scheme change
- Closed