We are using only Story points to estimate Technical tasks. * We would like to see on burndown chart the curve, based only on technical tasks (subtasks) of every user stories for given sprint. It can be the only one curve, or additional one. How to do it? * We expect to see velocity of our team as a sum of subtasks (not the tasks) done in given sprint. * On the sprint planning board we would like to see as a sum of the story points for new sprint only the sum of story points for opened subtasks (not only for opened tasks).

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

How to use estimations of subtasks in story points for burndown chart

Wòjcech Makùrôt2

We are using only Story points to estimate Technical tasks.

We would like to see on burndown chart the curve, based only on technical tasks (subtasks) of every user stories for given sprint. It can be the only one curve, or additional one. How to do it?
We expect to see velocity of our team as a sum of subtasks (not the tasks) done in given sprint.
On the sprint planning board we would like to see as a sum of the story points for new sprint only the sum of story points for opened subtasks (not only for opened tasks).

Accepted answers

sclowes

Hi,

There's no way to do this at present. I'd recommend enabling 'Time Tracking' then using the Remaining Estimate but encoding story points, for example '1h' = 1 story point, '8h' = 8 story points. This will allow you to do what you're looking for if you apply 0h estimates to the parent stories.

Thanks,
Shaun

All comments

sclowes

Hi,

Thanks,
Shaun

Ram Muthiah

"but encoding story points" in the above answer is confusing. Burndown chart should consider sub-tasks as well. Otherwise, there is no point in using sub-tasks. This is the major flaw in greenhopper.

AgentSmith

Greetings!

We have an existing feature request to reflect sub-task estimations on the burndown chart:

https://jira.atlassian.com/browse/GHS-6007

You might want to take a look at this one as well:

https://jira.atlassian.com/browse/GHS-5212

In the interim, you can configure a post-function in your workflow to set the remaining estimate to 0:

https://confluence.atlassian.com/display/JIRAKB/Set+Remaining+Estimate+to+0+on+post+function

I hope this info was helpful.

Cheers,
Jason | Atlassian

Korayem

That's not a solution at all because it will affect plugins that measure time tracking like Tempo.

Salem Korayem

We've solved this: during the sprint, the team updates Story Points field on parent issue by asking "how much points are their remaining?" resulting in points reduction or increase. This makes the chart burn down though the issue is still in progress