Different priority field values to different issue types

[Axel Holene]

I'd like to be able to associate one issue type with a given set of priorities, and another issue type with another set of priorities. 

Currently, all my customer's Priority field values are associated with bugs

• Blocker – blogcks development and/or testing work, production could not run
• Critical – Crashes, loss of data, severe memory leak
• Major – Major loss of function
• Minor – Minor loss of function, or other problem where easy workaround is present
• Trivial – Cosmetic problem like misspelt words or misaligned text

Which is fine for one issue type: Bug. It doesn't really fit in with for instance issue type Task, where "priority" should reflect whether or not this task has high priority or not. 

Of course, the simple answer would be to define some new Priorities, and live unhappily ever after with a mix of bug and task priorities in the same menu, though I'd rather say that, for instance, Task has it's own priorities. Is this possible?

[Thomas Schlegel]

Hi Alex,

this is one of the oldest and one of the most wanted issues in Jira. Have a look here: https://jira.atlassian.com/browse/JRASERVER-3821 and vote for it.

There is also a plugin that promises a solution: 

https://marketplace.atlassian.com/plugins/net.brokenbuild.project-priorities/server/overview

But it is not for free and only for server installations available.

[Axel Holene]

:-(

[Joe Pitt]

Another workaround is to create new custom fields for each issue type with the desired values and hide the priority field. Create a new priority of Not Used and set it as a default. 

[Susan Hauth _Jira Queen_]

HI Alex

We used the description field to clarify by request type what the priority definition is.  We added bold and color hoping our customers would read it.