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

Establishing Definitions For JIRA Issue Priority Levels On Scrum Projects

We have a priority scheme for our JIRA issue types for stories, tasks and bugs that include Low, Medium, High, Very High.  However, there is no organizational standard definition for these various priority levels.  So I'm trying to come up with some.  I am looking for any input from others if you have established priority definitions for different issue types that I might consider.

1 comment

Hi @John Bacon

That's a really good question, and there are multiple ways to approach this query.  As for my organisation's implementation, we mostly use the Jira Default priority values and MoSCoW in our priority field. However, that only encompasses prioritisation from Epic Level and below. Anything above the Epic Level uses a combination of those values and WSJF (you can easily do this via Jira automation or any automation out there).

I would suggest considering how prioritisation is conducted on items above epic, which could be OKRs or anything similar, as well as those under the epic level (stories and bugs). That should give you a good reference for what your organisation prefers to use, which saves you a bit of time when communicating any change management in the future.


Log in or Sign up to comment

Atlassian Community Events