Sub-task Time Tracking Doubled when added to new parent issue in active sprint

Summary

Sub-Task Estimation that is linked to a parent Story that is part of an active sprint is then moved to a new parent that is added to the sprint after start (Parent Story is a registered Scope Change event), the sub-tasks are also counted as scope change and the Estimate is doubled for each sub-task moved, as it does not ever Burn Down when removed from the original parent only burning up when it is added as a scope change event.

Environment

• JIRA Software Server
• JIRA Cloud Tested in v1000.773.2

Steps to Reproduce

1. Set Estimation Statistics to "Story Points"
2. Set Time Tracking to "Remaining Estimate and Time Spent"
3. Create Story with Subtasks that have estimation
4. Add this parent issue to a planed Sprint
5. Start the sprint
6. Add a new Story without Subtasks to the Sprint (This is an intentional Scope Change event)
7. Move a subtask from the Parent issue in the sprint at the time the sprint started to the new parent that is registered as a scope change event
8. View the Burndown Chart

Expected Results

Same behavior as Moving a Subtask between two Parent Issues that existed in the sprint at the time the sprint started the Estimation is not effected and continues to burn down as issues are completed

Actual Results

the Sub-tasks are also treated as a scope change event and the estimation is doubled for every sub-task moved to the new parent issue, as they are not removed from the original estimation

Notes:

If the issues are already counted as burn up, Move them back to the original Parent, this will not trigger an additional burn up but the value will still be inflated.

Workaround

If adding in intentional scope change for a story, make sure to move any subtasks to the issue before adding it to the active sprint to trigger a burn down with the sub-tasks before triggering the burn up with the parent and the sub-tasks together