Can't get an automation rule to trigger for a field changing

[Ste404]

Hi all,

I have an automation rule that triggers when the approver for an issue is changed, works perfectly if someone changes it on the agents view for the issue.

I also want it to fire when the approver field is first set via automation.

Basically when an issue is created, there is an automation that is run that populates the Approver from Assets based on certain conditions, this also works fine.

BUT if that newly set approver needs to be changed (the end result of the "Value changes for" automation)  should I be running a copy of the first automation just with a trigger of "issue created" but then what if it runs before the approver automation is run and sets the approver.

Not sure how to untangle this.

[Jens Schumacher - Released_so · Accepted solution]

The first rule can be activated by the second rule, but it is crucial to explicitly indicate that this rule can be activated by other rules in order to prevent infinite triggering loops.

See the screenshot below for where to find the setting.

[Ste404]

ah dammit.. I was certain I checked that box.  I checked it for the first one and not the second one..  what a dope!!

THANKS :D

Problem solved.

[Joseph Chung Yin]

@Ste404 -

Hi Steven:

I agreed with what @Jens Schumacher - Released_so suggested to the checkbox to "Allow rule trigger" option against your automation rules.

Another thing to use when debugging automation rule is write to the audit log (log action action setup) to see if the anticipated fields are being populated properly.

Here is a reference link on how to debug automation rules -

https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/

Hope this also helps.

Best, Joseph