Automation bugs with 'Time tracking' fields

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.


Making changes to Original and remaining Estimate in tandem reverts the value for the timetracking field which was changed first.


  • The first field gets updated as expected.

  • The second field updates as expected

  • The first field however reverts to the original value.

Automation rule to edit Original Estimate and Remaining Estimate
Automation rule impact on jira issue where it removes original estimate value


It is a bug in automation


Add in a re-fetch action in between the two operations and it works as expected.

Workaround of automation rule so that it does not clear up original estimate when remaining estimate is updated
JIRA issue history showing Original estimate and remaining estimate updated by automation

Updated on May 31, 2024

Still need help?

The Atlassian Community is here for you.