Automation bugs with 'Time tracking' fields
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
Making changes to Original and remaining Estimate in tandem reverts the value for the timetracking field which was changed first.
Diagnosis
The first field gets updated as expected.
The second field updates as expected
The first field however reverts to the original value.
Cause
It is a bug in automation
Solution
Add in a re-fetch action in between the two operations and it works as expected.
Updated on May 31, 2024
Was this helpful?
Still need help?
The Atlassian Community is here for you.