Issue with automation doing remaining estimate = original estimate - time spent

[rob_jeal]

I have some automation which seemed to work for a while doing the below. The issue that seems to be happening now is that the automation keeps cycling as it's seeing the remaining estimate field updating and then running again. 

WHEN

value changes for time tracking for edit issue

IF

{{timetracking.timespent}} does not equal Empty

THEN 

edit remaining estimate - 

{{#=}} ({{fieldChange.to}} - {{triggerIssue.fields.timetracking.timeSpentSeconds|0}})/60{{/}}m

Example of the cycling issue we're now seeing

[Trudy Claspill · Accepted solution]

Hello @rob_jeal 

The Log Work feature will automatically reduce the Remaining Estimate when time is logged if there is a Remaining Estimate value on the issue where the time is being logged.

What is the reason behind forcing that through an Automation Rule?

[rob_jeal]

Hi @Trudy Claspill  It was to capture changes to original estimate sorry. So if the original estimate is increased/decreased, the automation deducts time spent from the new original estimate, to provide the new remaining estimate.

[Trudy Claspill]

On the Rule Details page is this box checked, and if so was that a recent change?

That could cause the rule to be re-triggered because the rule itself is changing the time tracking data.

[rob_jeal]

Thanks @Trudy Claspill that is ticked but not a recent change but maybe the issue has been going on longer than I thought! I'll test it with that unchecked.. Thanks

[rob_jeal]

that seems to have worked, thank you!"

[Bill Sheboy]

Hi @rob_jeal 

Adding to Trudy's suggestions and your findings...

If that option to allow rule trigger was enabled for a while, perhaps it was selected incorrectly by a rule-writing person.  And thus their rules may be consuming your monthly, automation usage limit: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits

Please consider working with your Jira Site Admin to check usage and inventory all rules to determine if other rules have the setting enabled.  By default that option is disabled, and should only be used when you want the actions of one rule to trigger another.

Kind regards,
Bill