-
Suggestion
-
Resolution: Won't Do
-
1
-
12
-
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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
-
- Closed
- is incorporated by
-
- In Progress
- is related to
-
- Gathering Interest
- relates to
-
- Closed
- mentioned in
-
Page Failed to load
[JRACLOUD-4505] Assign schemes at the Project category level
Hi, in case you are up for a third party solution that's hosted by Atlassian.
Project Templates for Jira offers an intuitive way to design custom project templates and allow non-admins to create Jira projects based on them.
- Customize the templates configuration to meet your unique requirements
- Give non-admins template specific project creation power
- Customize the UX & information displayed to non-admins
- Clone project versions, components and project role actors
- Avoid the technical debt of unnecessary created Jira schemes/configurations
The app is built on Forge with no data egress, no sensible information stored and completely hosted in Atlassian's cloud infrastructure.
Please let our support know if you have any questions.
I vote for this or also add the capability to add a few custom fields to a project template would be incredibly helpful.
I hope this ticket makes it to production in 2021. I really would like to see the option to copy a scheme when creating a new project instead of sharing it.
When we want to make changes to a specific project we then have to create a different scheme it's very time-consuming.
Thanks
Denise
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.
Carl Blanchard
added a comment - - edited 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.
Deleted Account (Inactive)
added a comment - 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:
- Quickly add global component scheme (multiple schemes to choose from) to new projects
- Set global component leads in one step
- Component lead & default assignee (project lead, component lead, or unassigned) can be overridden at project level
- Ensure consistent naming (for filters, dashboards, & reports)
- 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)
Deleted Account (Inactive)
added a comment - 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:
Quickly add global component scheme (multiple schemes to choose from) to new projects
Set global component leads in one step
Component lead & default assignee (project lead, component lead, or unassigned) can be overridden at project level
Ensure consistent naming (for filters, dashboards, & reports)
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.
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. We understand that this is an important issue for many users, however, given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users, and enable us to move forward in a direction for Jira that provides the most value to customers.
After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Saskia van der Peet
svanderpeet@atlassian.com
Product Manager, Jira Cloud