How can I add sub tasks on burndown chart??

[Bárbara Monteiro de Barros Koch]

Hello all,

I saw many discussions about that but no solutions so far. My team need to have subtasks added at burndown to check story points per day.

Thank you 

[Mirek]

In short..

In Agile (Scrum) design you estimate stories. That is why estimation statistic is called a story point. When you implement Scrum you should set up backlog in such a way that your stories are relatively small to be able to complete in sprint (from 1 to 4 weeks depends how long is your sprint).

Breaking down stories into sub-tasks is good for the assignee of the work to have smaller pieces but story would be burn (burndown chart updated) only when it is completed. If it is not completed you have input for retrospective meeting why it is not completed and be able to improve in next sprint. That is how sprint by sprint you build team velocity and be able to plan and estimate more and more accurate.

Sub-tasks are good for tracking real time (in hours) and later compare this with other tasks to better estimate stories and break them down depends on team velocity and skills.

I hope it is clear what I am trying to say :)

[Nic Brough -Adaptavist-]

A short version of this is that you burndown when you deliver what you said you would.  Something is done or it is not, there's no (useful) in-between.

[Danut M _StonikByte_]

Hi @Bárbara Monteiro de Barros Koch ,

In the latest version of our Great Gadgets plugin, the sprint and release burndown gadgets have an option to include sub-tasks, which you could use to achieve what you want.  The plugin is available for both Jira Server (https://marketplace.atlassian.com/apps/1218777/great-gadgets-for-jira-server?hosting=server&tab=overview) & Jira Cloud (https://marketplace.atlassian.com/apps/1216564/great-gadgets-for-jira-cloud?hosting=cloud&tab=overview). 

Danut.

[Warren]

Hi

The generally accepted way of working with Scrum is to assign Story Points to the story (parent task) and hours to any sub-tasks. The Jira burndown is set up to account for this scenario.

I'm not aware of a way in Jira to get the burndown accumulating Story Points from sub-tasks. You could do it manually or automate it using the REST API - I'm not a huge fan of Jira's burndown so have long used the API to get the details out of Jira and create my own burndown.

I hope this helps

[Seemant Kulleen]

Do you happen to have a write up on how you did this?  I'd love to implement a burndown chart for my org, as the stock Jira burndown is extremely limited