Different priority field values to different issue types

Axel Holene June 14, 2017

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 for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Thomas Schlegel
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 14, 2017
TAGS
AUG Leaders

Atlassian Community Events