Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create a priority matrix using impact and urgency values - Next-gen Service Desk

I've been trying to setup our next-gen Service Desk so that the priority is automatically assigned based upon impact and urgency. I've attempted to create a workflow to reflect this, but the instructions only reflect how to do this in the previous generation of the Jira Service Desk. The part which is unclear to me is how to setup the workflow. The automation side of it should be okay, but I'm currently not able to set custom rule to to edit the priority (as the option isn't available) due to the absence of the matrix. 

Is anyone able to  help, please? 

2 answers

Sorry about the late drive-by post, but we just released an integration with Jira that helps you put Jira issues in a 2x2 priority matrix format. Perhaps this is of use to you? Drop me a line if you'd like to learn more.

0 votes

Hello @antony_major

Welcome to Atlassian Community!

Per your description, I understand that you would like to set the priority of the issues in your next-gen projects automatically based on the values chosen for two fields: Urgency and Impact. Is that correct?

If that's the case, I believe you can use only Automation for Jira cloud to achieve your need, not needing any workflow changes. Allow me to explain:

You can create two automation rules (Under project settings > Project Automation) that should be triggered when either one of the fields (Impact or Urgency) are filled, however, using conditions that only apply the priority update if both fields are filled with specific values. Check below two examples:

Screen Shot 2020-03-24 at 18.02.56.pngScreen Shot 2020-03-24 at 18.03.36.png

Using the rules above, the automation will be triggered whenever the Urgency or Impact are filled, however, it will only add any value to the priority field when both fields are filled, where you should be able to create different combinations to define the priority field.

For more information about Automation for Jira, check the documentation below:

Jira automation 

Let us know if this information helps.

Many thanks for sharing this with me. It is a great help. However, I'm currently looking at creating the SLA matrix initially and for the workflow to set the priority automatically based upon urgency and impact. The urgency and impact would be complete by the end-user in the self-service portal. I would like the workflow to then calculate the priority based upon what has been entered. There are details on how to do this in the "last gen" Service Desk, but not the next gen. 

Like Michael Santinon likes this

How would you compare this method to the Best Practice listed for Service Management at https://support.atlassian.com/jira-service-management-cloud/docs/how-impact-and-urgency-are-used-to-calculate-priority/ ?  Is there something about either method that makes one better for use in a Work Management project?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Submit your Jira Service Management use case and win!

Hi everyone - in case you haven’t heard, we’re hosting the show of the century on November 10th: High Velocity: ITSM World Tour.     This virtual, concert-themed experience...

275 views 1 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you