Burn down chart does not show the reflection for resolved sub task

[Chinthaka Perera]

Main Question : I have noticed that the sub task when moved to "Done" having completed the resolution screen, is not correctly reflected on the burndown chart created for the sprint ? the dips do not appear as expected and makes projections very complicated.

Back ground : I have set up the automation to calculate the child (sub) task and update the Story as well and this is working. Mine is a company managed project and runs on story points.

Any one noticed the same ? and is there a fix ?

[Laurie Sciutti]

Hi @Chinthaka Perera and welcome to the Community.  The burndown chart tracks the remaining work in the sprint at the Story-level.  Sub-tasks are a break-down of Story-level issues so they are not included in burndown charts.

[Chinthaka Perera]

Hi @Laurie Sciutti thank you for the response, is there a way we can reflect this at a sub task level, where visual progress can be seen more frequently ? as JiRa does allow for the sub task to be estimated and accumulated to the story .

[Cliff Stovich]

I think the easiest fix would be to put the sub tasks into a story and have an automation rule that closes the story once all tasks/subtasks are complete. You would have to assign story points to the story and not it's subtasks I believe. 

[Danut M _StonikByte_]

Hi @Chinthaka Perera,

Indeed,  the Jira reports (sprint, burndown, velocity) do not consider the sub-tasks estimates.

Fortunately, you can easily solve this by using our Great Gadgets app.  It offers advanced dashboard gadgets (sprint burndown /burnup, release burndown/burnup, velocity) that allow tracking agile projects and they have the option to include the sub-tasks in the calculation. No extra work on Jira automation is needed. 

Sprint Burndown Chart with subtasks

Release Burndown Chart with subtasks and forecast / projection 

I hope this helps. If you need any help on setting this up, please contact us at support@stonikbyte.com.

Thank you,

Danut Manda