Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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?


Imagine you have 10 projects, each with an average of 4 different priorities.

You now have 40 priorities for everyone to search through.  Many users won't know which one is most appropriate for any particular project.  Actually, that example works with just 2 sets of 4 priorities.

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?


Log in or Sign up to comment

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you