nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Should Burnup report include the Story Points from sub-tasks?

Mikhail Davydov_gfpnkr

Hi All,

I find the new Jira Burnup report to be better than previous Burndown, as it feels better when you are going up

However, at this point, Burnup includes only the Story Point Estimates from Tasks, but not from Sub-Tasks, which makes Sub-Tasks estimates to be useless.

Is there any way to make Burnup chart to include Sub-Task Estimates?

Best regards,

Mikail

Comments

Warren_mz9b4z

Hi @Mikhail Davydov

Generally in Scrum, parent tickets (Tasks etc.) will have an estimate in Story Points and sub-tasks will have an estimate in hours. You can choose to either burndown or burnup of the sum of the hours on all sub-tasks or the sum of story points on all parents.

If a Task is broken down into sub-tasks, you haven't achieved any value until all sub-tasks are complete, which is why story point burndown or up is based on the parent only.

Nic Brough -Adaptavist-

No, it should not include sub-task estimates.

When you're doing Scrum, the burn-down and burn-up are a measure of what you said you were going to do when you went into the sprint. You commit to doing a set of issues, and the question for the burn reporting is "is what you committed to done or not"? There is no partial done, your product owner does not care if 0%, 1% or 99.99% of the sub-tasks are done, the issue is not done until the story is done, and that's why burn reports should only look at the story level.

(Internally, a team may well find estimates on sub-tasks might tell them something useful during a sprint, but because the burn reports are for reporting on completion of stories committed to, the sub-tasks are irrelevant)

Mikhail Davydov_gfpnkr

Thanks for a great explanation! All is clear now.

Mikhail Davydov_gfpnkr

Thank you for the clarification!

Danut M _StonikByte_

Hi @Mikhail Davydov ,

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.

Mikhail Davydov_gfpnkr

Thank you Danut!
I probably will check it out after testing the flow suggested above.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

burnup