Automation triggers on field upadate before field is actualy updated in Data Base

[דניאל שוקרון]

Hi,

I developed "Risk Management" Automation rule. I've created 3 custom fields, of number type. 1. Risk Likelyhood, 2. Risk Impact, 3. Risk Score. The Automation rule is triggered if/when Risk Likelyhood/Impact is changed. The Action calculates the multiplication of Risk Impact in Risk Likelyhood and the result value is stored in Risk Score field. Then, a case if/else block checks are perfomed to determin/set the value in "Priority" field acording to the value of Risk Score field. 

The problem I'm facing is that when the Automation rule is triggered and beeing excuted, because of filed value change, the values in 1. Risk Likelyhood, 2. Risk Impac custom fields are correct, BUT the value of 3. Risk Score, is of the previous values were in 1,2 and not the new/current values. 

If Risk Impact was 3 and now 5 and Risk Likelyhood was 5 and now 4, the value of Risk Score compared by the Automation rule is 15 (old value) and not 20 (new value).

AI is suggesting differant ideas, many of them are not even available in Jira (like delays)....

Any suggetion how I can overcome this ?

[Fede Baronti -Deiser-]

Hi @דניאל שוקרון , 

Welcome to the Atlassian Community. Thanks for your post.

Automation for Jira has an action that allows you to re-fetch Work Item information just for these types of cases. It's called: "Re-fetch work Item data".

As it says in the action explanation, this will help you in case you need the latest state of a work item in subsequent actions in the flow. I believe that your use case would benefit from this action. 

Including this action (Re-fetch) before the Action that calculates the multiplication of risk should allow the calculation to operate with all the latest data. 

I hope this helps, and please don't hesitate to let me know if there are any further questions.

Cheers, 

Fede.