Automation - Original Estimate updating Remaining Estimate but it shouldn't

[Matej Stolfa]

I have setup an automation rule that updates field 

"Original Estimate" based on the ticket type. 

In the automation, it specifically states that 

"Changing Original Estimate will not automatically adjust the value of Remaining Estimate."

But this does not seem to be the case.

Automation sets "Original Estimate" correctly based on the rules, but then for unknow reason sets the "Remaining Estimate" to 0m

[Alex Koxaras _Relational_ · Accepted solution]

Hi @Matej Stolfa 

From the tests I've made on my instance here are my results:

• When entering original estimate for the first time, while remaining estimate was null then indeed the automation was setting the remaining estimate to 0.
• When I logged in time and then set the original estimate again, then the remaining estimate was not changed.

Now since these two fields are connected to each other, I believe that this was made on purpose. Remaining estimate is set to 0, in order to be unchangeable by your change on original estimate.

[Matej Stolfa]

Thank you @Alex Koxaras _Relational_ .

Yes, this is indeed what is happening. 

I have resolved it by setting both values at the same time. 

e.g. if both Original Estimate and Remaining estimate are 0 (as they are in all new tickets) I'm setting the value for both fields. 

[Vikrant Yadav]

Hi @Matej Stolfa  Welcome to Atlassian Community!

As per the screenshot, it seems that some issue in Automation rule. You are trying to set 4h Original estimate but automation is setting it 1D , is it correct ? 

Remaining estimate is calculate automatically based on Time Spent on issue, yeah it's possible to set manually, but usually Remaining estimate calculated based on Time Spent field. 

Check if any other rule in the project which is setting Remaining Estimate ? 

If you selected only Original Estimate then Automation set only Original Estimate.

[Matej Stolfa]

Thank you @Vikrant Yadav , 

Apologies for the confusing screenshot, the issue is not that is is set to 1d. 

There are different rules and the Original estimate is then updated as a result. 

The real issue is that "Remaining estimate" is also automatically updated. 

It looks like the rule just updates both fields but is shouldn't. 

I have reviewed all the project and global rules, nothing is set to change the Remaining Estimate. 

It should be as you say, calculated from the logged hours. So I don't know where the second automation is coming from...

[Vikrant Yadav]

Let me add Automation expert of this because i am not able to reproduce the same issue on my instance. 

@Bill Sheboy @William Sheboy  Hi Bill, can you please help @Matej Stolfa  in Automation rule ?