nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Former user

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

{{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

Screenshot 2024-09-10 141453.png

Accepted answers

Trudy P Claspill

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?

All comments

Trudy P Claspill

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?

Former user

Hi @Trudy P 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 P Claspill

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

Screenshot 2024-09-11 at 1.06.51 AM.png

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

Former user

Thanks @Trudy P 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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud