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

Can story points on subtasks roll up to stories and be used for the burndown chart?

jeeinerson

We normally have four or five subtasks in our stories. We don't get credit on the burndown until all substasks are closed and the story is closed. Can we add story points to the subtasks and not the story and then have them roll up to the story? If so, will the burndown chart show the burndown as the subtasks are closed or do you still have to close the story to have it start to show on the burndown?

Accepted answers

Nic Brough -Adaptavist-

No. Estimates do not go on sub-tasks and even if you decided to do them (and code for rolling up as Jira won't do it), they will not count in burn-down. Burn down measures how you are doing compared to what you committed to. You commit to delivering stories, not sub-tasks.

All comments

Nic Brough -Adaptavist-

jeeinerson

Thank you, Nic!

Mike Wilkins_dhkhnu

@Nic Brough -Adaptavist- I understand and agree that you commit to completed stories, not sub-tasks, so why does the sub-task contain the story point field?

Jira allows you to split a story, so if you came to the end of a sprint, and you still had one or two sub-tasks incomplete, you could split the story into a new story containing the incomplete tasks and claim the completed sub-tasks (but this is against the spirit of Scrum - I know, I know!)

Nic Brough -Adaptavist-

Because someone has added the story points to the sub-tasks. They're not there by default.