Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,332,688
Community Members
 
Community Events
169
Community Groups

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

We are using only Story points to estimate Technical tasks.

  1. 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?
  2. We expect to see velocity of our team as a sum of subtasks (not the tasks) done in given sprint.
  3. 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).

4 answers

1 accepted

2 votes
Answer accepted

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

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

2 votes
AgentSmith Atlassian Team May 14, 2013

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

"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.

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 :)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

3,058 views 7 25
Read article

Atlassian Community Events