Priority values need to show up based on the custom field Severity values.

Samuel Prathipaty May 14, 2023

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?

1 answer

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Hi @Samuel Prathipaty,

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:

  • Trigger: issue ceated
  • Conditions: e.g. impact is high and urgency is high, then Priority -> P1 (and so on)

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events