Can we get sub tasks added to sprint burn down or velocity chart

[Sujala]

Hi 

Jira's default hierarchy for team-based soft project seems to be. 

Epic -> User story - Sub-task

Our team wants to estimate sub-tasks using story points, and then we want to measure our velocity and sprint burn-down chart using subtasks.

Can we do that in Jira?

The default Sprint burn-down charts and velocity reports do not seem to consider sub-tasks which is really frustrating.

Any ideas or workaround?

[Frederik Vantroys]

Hi @Sujala ,

* One workaround could be to consider epics as stories and stories as subtasks. Of course when you really need real epics that's not an option

* Another way to go would be to make a custom field for the sub task type 'story points for subtasks" and use that to put in the estimates. you could then put the sum of the SP in the parent or make an automation rule that updates the sum for you every time you fill in your custom field.

[Danut M _StonikByte_]

Hi @Sujala,

Indeed, Jira does not consider the subtasks in burdown and velocity chart. 

Fortunately, there is a good solution for this. Our Great Gadgets app offers all the gadgets needed for tracking agile projects (release burndown, sprint burndown, velocity chart, etc) with subtasks support. They work with any type of estimates.

Have a look over these blog articles to make an idea: 

• 7 gadgets for a powerful Scrum dashboard in Jira 
• How to track multi-team or scaled-agile projects (such as SAFe®) in Jira with Great Gadgets app 

This app offers many other gadgets that you will find useful.  

If you have questions, please don't hesitate to contact us at support@stonikbyte.com.

Thank you,

Danut Manda

[Bill Sheboy]

Hi @Sujala 

What problem are you trying to solve by doing this?  That is, "why do this"?

User stories are often considered the smallest piece of valuable work that can be released to production.

Subtasks are often considered a piece of work to complete something, like a user story.  They are not typically individually releasable to production.

Story points are often considered a way to assess the effort, complexity, etc. for a user story...so that a team can confirm shared understanding of the work.

If you instead want to track work to a lower level, consider using effort hours for subtasks, or if your team's understanding of "subtasks" is they are individually releasable, just skip that level and only use Epics and Stories.

Kind regards,
Bill

[Sujala]

Thank you for your time and effort in replying to this.