Priority Schemes in JIRA

[Victor Mutambuki _Mumo Systems_]

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?

[Nic Brough -Adaptavist-]

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.

[Victor Mutambuki _Mumo Systems_]

thanks

[Pronto Software]

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?