-
Bug
-
Resolution: Fixed
-
Low
-
8
-
Severity 3 - Minor
-
Hi everyone,
We have now resolved this bug by introducing the following logic. The original time and remaining time fields will remain in sync, if the original time is changed after it is first entered, the remaining time will also change. However, once time is logged or if the remaining time is manually updated, this sync will no longer occur i.e. the remaining time will no longer change when the original time is updated.
Thanks
Tha Atlassian Cloud team
Issue Summary
The Remaining estimate is not updated when the Original estimate is filled on the issue.
Steps to Reproduce
- Enable the new issue view on the Profile Settings
- Add Time Tracking to the issue's edit screen
- Create a new issue
- Open the issue and enter a value on Time estimate
Expected Results
Remaining estimate receives the same value as Time estimate
Actual Results
Remaining estimate is not updated
Workaround
This specifically happens on the new issue view only. You can either permanently disable the new issue view on your Personal Settings or temporarily with the See the old view button
- has a derivative of
-
JRACLOUD-93429 Remaining estimate is not updated when original estimate is filled on the issue
-
- Closed
-
- relates to
-
JRACLOUD-71603 Re-occurrence of JRACLOUD-71004 - Remaining estimate is not updated when original estimate is filled on the issue
-
- Closed
-
-
JRACLOUD-93264 Time remaining should change based on changes made to Original estimate
-
- Gathering Impact
-
- is resolved by
-
BENTO-6220 Loading...