It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

Wòjcech Makùrôt Nov 05, 2012

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

Korayem May 26, 2013

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

2 votes
Ram Muthiah Apr 26, 2013

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

2 votes
Jason Worley 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

0 votes
Salem Korayem Jun 13, 2013

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
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

1,334 views 1 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you