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; } } }

Is there any way to have child issues count toward the burndown?

Debi.Damas

I am new to this product and want to create an accurate burndown report. I cannot see where child issues contribute to the burndown, or the issue count resolution. Why is this? Am I missing something? My burndown reports are kind of useless at this point. If I want to make my sprint management and Epics look totally messy, I could do this, but if the child issues don't burn down, what use are they?

Accepted answers

Ravi Sagar _Sparxsys_

Hi @Debi.Damas

The Burndown report that comes with the board won't consider sub-tasks (in case you are estimating story points at sub-task level)

You can try using eazyBI and build a custom report or export your issues in a spreadsheet and create reports there. I know it is not ideal.

Ravi

All comments

Ravi Sagar _Sparxsys_

Hi @Debi.Damas

The Burndown report that comes with the board won't consider sub-tasks (in case you are estimating story points at sub-task level)

You can try using eazyBI and build a custom report or export your issues in a spreadsheet and create reports there. I know it is not ideal.

Ravi

Debi.Damas

Thanks, Ravi. You are right, that is not idea. To me defeats the purpose of putting story points on or even having sub issues. Is there any thought to adding this functionality? I think it would make the product much more valuable.

Ravi Sagar _Sparxsys_

There is already a discussion on this topic - whether you should estimate at story point level or not.

Since you are on cloud take a look at Portfolio for Jira, it can help in aggregating the story points from lower level in the hierarchy to upper ones. It is more geared toward scheduling and making a plan but it will let you organise issues in hierarchy like Story > Epic > Initiative

Ravi

Nic Brough -Adaptavist-

Jira is heavily aimed at Scrum or Kanban.

Neither of those methodologies do sub-task estimates. One big point of Kanban is that every object is the same size, so you don't need estimates beyond "number of cards". With Scrum, you are supposed to be telling the world "we're going to do these stories". You don't promise sub-tasks to your product owners (they don't care), so you don't estimate them.

So, no, sub-task estimates on burn-down is not under consideration, because it's not LEAN/Agile/Scrum/Kanban/etc.

There are tricks you can play if you think estimates on sub-tasks are useful, but you do have to be careful about how you implement them. The obvious one "add up points on sub-tasks to their parent" fails badly in Jira, for example.

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