Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Priority Schemes in JIRA

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