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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Priority - P1,P2,P3,P4 and Severity - Sev1,Sev2,Sev3,Sev4
For issues that have a severity of Sev 1, P1 have to be the only acceptable priority. For issues that have a severity of Sev2, P1 and P2 have to be the only acceptable priorities,....
We need priority values to shown/acceptable based on the Severity values. How can we achieve this?
A common practice is to calculate the priority automatically from a combination of impact and urgency (or a combination of more objective criteria you prefer).
Since the Priority field is a system field, you cannot make it dependent on another field (at least not of the box and marketplace apps still have limited capabilities in that area as well).
If you add these fields to the create screen of your issues, while removing the priority field (If you use Jira Service Management, rather do this on the portal request forms), you can use automation to calculate the resulting priority without your users being able to select an unwanted priority there.
All you need to do then is determine what combination of values results in a P1, P2, ... and build your automation around that:
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.