-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: Work Item - Backend - Worklog
-
2
-
Severity 3 - Minor
Issue Summary
Editing a worklog incorrectly updates the original entry in the issue history
Steps to Reproduce
- Log work into an issue.
- Check the issue history of the issue and you will usually see 3 new entries:
- (Total) Time spent updated
- The "Remaining Estimate" being updated (optional)
- User logged x amount of time (corresponding to the work logged in step one.
- Go to the Worklog tab and edit the worklog, decreasing time indicated in it, and save changes.
- Go to the issue history again and check the 2/3 new entries, but also look at the entries from step 2.
Expected Results
The entries added during step 2 remain the same, and 3 new entries are added to reflect the update in the worklog, allowing the history to remain consistent and for users to understand the chronology of the changes.
Actual Results
From the entries added from step 2, the "<User> logged x amount of time" is also updated to the same time as the updated time in the worklog, meaning the original time logged is lost and the issue history is no longer consistent.
Demonstration: Work Log Update.mp4![]()
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available