Different priority field values to different issue types Edited

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?

1 answer

Comments Closed
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jun 14, 2018 in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

787 views 5 7
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you