Impact of moving a sub-task to a story in regards to burndown chart

[bschmi]

Hi community,

a colleague approached my with the following question but I was not able to get to the bottom of the case.

Given a scrum board a subtask was moved to a story. Now it seems not to have an impact on the burndown chart.

Is this somewhat expected behaviour?

Thanks,
Birgit

[Ste Wright · Accepted solution]

Hi @bschmi 

It depends on which statistic option is selected for the burndown chart.

Burndown charts show issues which are standard issue types (bar Epics, which is a special case).

If the statistic selected for the report is issue count, when the sub-task is converted to story it should display as scope change within the burndown.

However, if the statistic is story points, then converting the sub-task might not have any impact if it has no estimation. It would need to have story points added to it after conversion to impact the scope on the burndown chart.

Does this help? If you're finding this behaviour isn't working as expected, let us know some more specifics so we can help further :)

Ste

[aswathi.jc]

We're seeing this instance where:

1. A story was slotted into a future sprint
2. Sub-tasks within the story were converted to new stories. [These were automatically created into the same future sprint as the parent story]
3. Story Points were assigned to each of the stories (created by converting sub-tasks)
4. Sprint was started
5. The stories (created by converting subtasks) are NOT showing up in burndown or sprint reports.

[Ste Wright]

Hi @aswathi.jc 

Could you attach a screenshot, specifying where this is happening?

It can also help clarify how you have the reports setup :)

Ste