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; } } }

Why is an automation targted at the remaining estimate is affecting the original estimate

Jacques Dussault

On a scheduled automation nightly, on specific issues (JQL), the automation reduces the remaining estimate by 10% of the original estimate (and so by the end of a 10 days sprint, to 0h)

This is the JSON I use :

{ "fields": { "timetracking": { "remainingEstimate": "{{#=}} {{issue.timetracking.remainingEstimateSeconds}} /3600 - ({{issue.timetracking.originalEstimateSeconds}} * 0.1) / 3600 {{/}}h" } } }

The issue is : for some reasons , it also edit the original estimate with the same rule and I can not find why it is doing that.

Any idea? Screenshot 2024-06-17 144822.png

Accepted answers

Jacques Dussault

After review by the Atlassian Support and Dev Team, there is actually a bug.

They provided simple workarounds .

You can find all the details here : https://jira.atlassian.com/browse/AUTO-1328

All comments

Bill Sheboy

Hi @Jacques Dussault

First thing I notice is your rule's Edit Issue action is trying to edit the Remaining Estimate field twice:

once by selecting it from the dropdown list
and once in the advanced edit with JSON.

Only one of those may be used in a single edit action for the same field.

Please try removing that and retesting to observe the impact, perhaps with some test issues. (You could temporarily modify your trigger's JQL to only include testing issues to help debug this symptom, and then revert it once fixed.)

Kind regards,
Bill

Jacques Dussault

Thank you for flaging the double edit. I corrected that. Sadly, that does not seem to be the reason why the original estimate gets updated too.

I'm already working on a restricted amound of issue (2) and theyr are both behaving the same way.

Bill Sheboy

Please post an image of the audit log details showing the rule execution and of the issue's change history showing the changes.

And, what changes in value do you notice in the Original Estimate field when the rule runs?

Jacques Dussault

After review by the Atlassian Support and Dev Team, there is actually a bug.

They provided simple workarounds .

You can find all the details here : https://jira.atlassian.com/browse/AUTO-1328

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