Refreshing Values

[Devon Engen]

Ok - I'm going to give describing this scenario a go. I have a select list (single choice) custom field called LOE. Using automation, I create a lookup table to assign a value to a DIFFERENT custom field called LOEValue based on the selection from the LOE field. The field assignment is working BUT if someone were to update the LOE field selection choice, the value populated in the LOEvalue field does not update. Is there a way to edit the automation to update that value if the LOE field is changed? 

[Trudy Claspill · Accepted solution]

Hello @Devon Engen 

Welcome to the Atlassian community.

When asking for help with an automation rule, it will better enable us to help you if you provide screen images that show the entire automation rule you have.

One piece of information you left out is what is the trigger for your current rule?

There is a Field Value Changed trigger that you can use to monitor for changes in the LOE field and then execute the steps to create the Lookup Table and set the LOEValue field.

[Devon Engen]

Here is the automation - it's pretty basic, Would the field value changed trigger need to be another automation? I have 6 fields total so I'd need an automation for each field & it's lookup table/assignment and another one for the value changed trigger?

[Trudy Claspill]

The Field Value Changed trigger catches the change to the field during issue creation. You don't need a rule triggered by Issue Created and a separate rule triggered by Field Value Changed.

I would recommend using a separate rule for each field.

With the Field Value Changed trigger you can identify multiple fields to monitor for change. However you might then need to add logic to the rule to figure out which fields actually changed. That would add complexity to the rule.

If you use a separate rule for each field, the rule will trigger only if the one specified field changed.

[Devon Engen]

I'm a bit confused since I'm trying to run an automation if a field is changed AFTER the issue was created? Sounds like this isn't possible? 

[Trudy Claspill]

Incorrect.

Your current rule is triggered by issue created, and sets the LOEValue field based on the LOE field. When the issue is created the value of the LOE field changes from null to the value you selected.

Additionally the field value can be change on an existing issue by editing the issue.

The Field Value Changed trigger can detect both change scenarios, eliminating the need for a separate rule triggered by Issue Created.

If you want to have a rule triggered by Issue Created and another that is triggered only when an existing issue is edited, then the second rule can use the Field Value Changed trigger and you can set the For Operations field to just Edit Issue.

[Devon Engen]

That worked!!!! Thank you SO MUCH

[Trudy Claspill]

You're welcome!

[Bill Sheboy]

Hi @Devon Engen -- Welcome to the Atlassian Community!

It is possible to do this with one or two rules.

With one rule using the Multiple Issue Event trigger, select both issue created and updated.  Normally, I do not recommend using this multiple event trigger, however for this scenario having one rule will reduce the maintenance risks of the lookup table getting out of sync between rules.

The "trick" is the rule needs to check the {{eventType}} and {{changelog}} so it only updates the LOE_Value field when:

• the {{eventType}} smart value equals "jira:issue_created:issue_created", indicating it was an issue creation that triggered the rule, OR
• the {{eventType}} smart value equals "jira:issue_updated:issue_updated" AND the only entry in the {{changelog}} is your custom field, indicating it was an edit

Kind regards,
Bill