You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.