Trying to automate Priority Calculation based on Impact and Urgency

Hi @charu 

Your rule image is a bit low-resolution, and it looks like you are using conditions, one after another.  In that case, when the first condition fails the rule will stop processing.

There are several ways to solve your scenario, including at least these:

1. Use an IF / ELSE block with the conditions for each case, ensuring they are mutually exclusive and in the order you want to test them.  Then the rule will continue until it finds a match...or runs out of cases to check
2. Use a Lookup Table, where you concatenate the test values as keys, such as "Low Impact--High Urgency", creating a table row for each combination with the Priority stored in the row's value.  Then the rule would be only about four steps, using the table's get() function to find the priority.

I recommend the second approach as the rule will be easier to understand and maintain.

Kind regards,
Bill

Hello @charu 

Welcome to the Atlassian community.

When a rule execute it creates an Audit Log entry with the details of the execution. You can get to those by clicking on the Audit Log link in the rule UI.

An entry is created each time the rule is triggered and each time the rule is changed and saved. Find the entry for when you changed the Urgency and/or Impact values and click the ">" character on the right to expand that entry.

Then click all the ">" characters within the entry to expand all the details for what occurred when the rule executed.

Share with us a screen image of what you get.

I believe I know what the problem is.

When you use a simple IF condition in your rule, the first condition encountered that does not match will cause the rule to stop running.

If the values for Impact and Urgency cause the issue to not match the first Condition in your rule, your rule will stop running. It will not check any of the other conditions. In the Audit Log you would see something like this:

I got the above with the rule below, when I changed the Priority value in the issue from Low to High.

Because the Priority value did not match Low when this rule was triggered, the rule stopped running when the first condition did not pass. No steps after that were executed.

Instead you need to use the If-Else Condition block.

That enables you to create a structure where if the first condition doesn't match then the rule will proceed to check if the second condition matches. If the second condition doesn't match then it will move on to the third condition, and so on, until it finds a Condition that does match.

After creating the first condition and the steps to execute when that condition passes, then click the Add Else button below the Add component button.

Add you second condition and the steps to execute when that passes. 

Repeat the steps to add all your conditions and their accompanying steps.

Then in your rule execution audit log you will see entries for each condition that it checks that it doesn't match until it comes to the condition that it does match.

Hi @charu , Welcome to the Community!

Have you looked at this Community page yet? @Jovin's  answer should help:

https://community.atlassian.com/forums/Jira-Service-Management/Automate-Priority-Calculation-Impact-and-Urgency-Based-Task/qaq-p/2899473

I can see in your automation that it should use IF-ELSE instead of just a straight series of IF statements and actions -- the way it's set up now, if it meets the criteria of the first IF statement, then it sets the priority to 'Highest' but if it doesn't meet that criteria, it just stops. When you use a series of IF-ELSE statements, if the first set of criteria doesn't match, the automation will continue to the next IF statement etc. until if finds an IF statement that matches and then it'll take action. The Community page above will provide an example.

Let us know if that works!