I'm trying to understand what's the purpose of having the priority scheme editable rather than having the default priority scheme working for all projects. Why not just select the level that suites an issue and ignore the rest. Why have it editable?
thanks
Prior to Priority Schemes coming along, all projects have the Default Scheme (with basic Priorities). Now we have Priority Schemes, I’d like to add a few new Priority types for specific projects. Great, I create new Priorities, create a Priority Scheme, add the Priorities to the Scheme.
Problem: the new Priorities exist in the Default Priority Scheme, which can’t be edited, so all Projects get extra Priorities that don’t relate to their issues.
I can’t create a new “instance default” Priority Scheme and associate all the Projects to it – as you do for other types of Schemes - you can only have one Project per Priority Scheme. There’s no way we’re going to manually create one Scheme per Project in order to move them away from the Jira Default Priority Scheme.
Any ideas about handling this?
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira
Explore the interface and basic Jira terms, then discover how to effectively manage your work.
Learning Path
Atlassian tools and practices for developers
Focus on your development work by using Jira software features and functions efficiently.
Atlassian Certified Associate
Jira Software Essentials certification
Demonstrate proficiency in utilizing essential Jira features and working efficiently with Agile frameworks like Kanban and Scrum.