Automation rule on Version update Looping

Question

I am trying to create an automation rule to detect when the Version Driver field on a Jira Version is changed so that I can send a web request to an external system.

However, the "Version Driver" feature, has not yet been fully integrated into Jira's REST API yet which means a) there is no smart value for the version's driver property and b) a change to the version Driver field does not trigger an automation that is triggered by a Version update.

But I can still get it using the expand parameter as follows

/rest/api/3/version/<version_id>?expand=driver

So I am implementing a workaround, whereby a user can update the Version Description when they have changed the Version Driver, which means an automation triggering on Version update can run.  However, as part of this I then want to update the Version Description (this is to remove a trigger text string "update version driver", that I am using in the Description to limit running the body of the automation so it only runs when a user makes a Version driver change.  However, because I am updating the description (to remove that text string), my automation continuously triggers and goes into a loop even though I have unchecked  "Check to allow other rule actions to trigger this rule". Is there anyway I can stop this rule triggering itself ? - it is a change to a Version driver than I am trying to detect.  The screenshots are of an abbreviated automation to demonstrate the problem

Rees, Ian · Answer

Hi Bill,

thanks for the reply and just wanted to acknowledge it and I will come back and try your solution. I moved onto doing it another way but will still complete this to help my understanding.  I will reply when I can rerun. Thanks

Bill Sheboy · Answer

Hi @Rees, Ian

Would you please post an image of the audit log details, showing an example where the rule is "looping" and repeatedly triggering?

From what you described, I would hypothesize the rule triggers only twice:

* when the triggering text of "update version driver" is entered into the version's Description
* when the triggering text is removed

And...to manage the rule triggering / processing, a smart value condition on the changes could be used to determine when that triggering text is added versus removed.

Kind regards,
Bill