-
Bug
-
Resolution: Won't Fix
-
Low
-
5
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Issue Summary
When a user clones an issue, it is expected that all information related to time tracking are not cloned as stated in our documentation here.
* Time tracking * Comments * Issue history * Links to Confluence pages
Expected Result
JIRA clones the issue but does not clone values from fields related to time tracking.
Actual Result
JIRA clones the issue as well as the values of the time tracking field.
Workaround
Clear the content of the time tracking fields after the Clone issue has been created
EDIT 12/23/2024 - This does not appear to fully clear out metadata at all under the following scenarios, reopening bug report as this is still causing issues with no resolution:
1. Sub-task parent is changed. This happens when a story needs to be split – some sub-tasks remain with the original story and some are moved to a new story. The sub-tasks below are from the new story.
- The sum field is the entries at the issue level displayed (in this case sub-task) + entries at the child level. Since there is no child of sub-tasks, the Remaining Estimate should be the same for Remaining and Sum of Remaining.
- The entirety of the data remains with the original parent despite some of the sub-tasks being removed form that parent and aligned to another.
This happens with the Original Estimate and the Remaining Estimate, but not the Time Spent. This data appears all the way up through the hierarchy although no entries are made on those levels.
2. Story cloned with Original Estimate on the sub-task level. This work is still in the Backlog so no time has been entered. We have discovered that Cloning doubles the OE and the Remaining Estimate in the new story.
- is related to
-
-
- Gathering Impact
-