Sub-tasks added to Active sprints are considered Scope Change if Remaining Estimate and Time Spent is enabled

Ticket for documentation to be updated.

Steps to reproduce

• create a Scrum board with some issues
• create a Sprint and add these issues to it
• configure the board to use Story Points for estimation
• enable Remaining Estimate and Time Spent for estimation
• estimate the issues and start the Sprint
• now that the sprint is Active, add a sub-task to one of the issues
• go to Burndown Chart, this sub-task is displayed as a scope change
• now disable Remaining Estimate and Time Spent
• go to Burndown Chart, sub-task is not displayed any more

Suggestion

This is not a bug:

• the Burndown Chart are to be designed to work that way (toggling sub-task display) depending on whether Remaining Estimate and Time Spent is enabled or not
  • Time estimates are rolled-up from sub-tasks to the parent task.
• the fact that sub-tasks are treated as scope change, if created in an Active sprint, sounds logical

However, these behaviors do not seem to be documented anywhere in JIRA Agile documentation, including:

• Estimating an Issue
• Configuring Estimation and Tracking
• Tutorial - Planning and Estimating work for an Agile team