Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.1.9
-
7.01
-
2
-
Severity 3 - Minor
-
0
-
Description
Summary
When cloning an issue with Time Tracking data, the time remaining/estimated is copied incorrectly.
Environment
- JIRA 7.1.9
Steps to Reproduce
- Create a new story with an 8 hour estimation.
- Log 1 hour of time on story.
- Create a sub task off of that issue with 2 hour estimation.
- Log 1 hour on that sub task.
- Check total estimated time on original story is 1d2h (assuming the default 8 hour workday).
- Remaining time on original story is 1d (1d2h -1h -1h).
- Now clone the Story, you will see remaining time as 2d, with and estimated time of 1d 2h.
Expected Results
Either it will not clone the time at all, as documented (see https://jira.atlassian.com/browse/JRA-34366 and https://jira.atlassian.com/browse/JRA-60361), or that the remaining time will stay consistent.
Actual Results
The remaining time is set to an incorrect value, that can exceed the estimated time.
Attachments
Issue Links
- relates to
-
JRASERVER-34366 Regression: "Clone Issue" action Clones Original Estimate field value
- Gathering Impact
-
JRASERVER-60361 Clone issue copies time tracking
- Gathering Impact