Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Burndown on time estimate from subtask - how to get it to work?

Hi.

I was wondering if anyone knows how to get the burndown to work if possible when using the "Original Time Estimate" rather than showing burndown on "Story Points"? (Note that "original time estimate" is the same as "time estimate" at least when sprint starts) Currently, in Jira Cloud version, you can select "Story Points", "Business Value", "Issue Count" and "Original Time Estimate". 

Usually when burning down on "Story Points" it takes maybe a few days before a story is closed. So the graph is usually the same for a few days before it reflects the work. We would however like a daily feedback on how much progress has been made, i.e. how many/big subtasks have been closed.

WHAT WORKS:

If you put a time estimate on the Story (parent) the burndown on "Orignal Time Estimate" works. 

WHAT DOES NOT WORK:

You put time estimate on subtasks (chidren), you make sure you opt for "Include sub-tasks" in time estimate on the story/parent. The rollup to parent works, if you open up the story, it includes the time estimate from the childrent/sub-tasks, but in burndown, it always stays on zero, unless you put a time estimate on the parent it self. But this is the same as putting a story point and as stated before, we would like a daily burndown that reflects closing of subtasks much faster. (And using "Issue Count" as a burndown metric is not an option since it does not reflect how much of the work has been completed in terms on time/size)

 

Any help is appreciated.

 

3 answers

1 vote

Hello @mirelm

Your requirement has been discussed many times before on this fourm, please see the following threads

https://community.atlassian.com/t5/Jira-Software-questions/Story-points-subtasks-gt-burndown-chart/qaq-p/178924

https://community.atlassian.com/t5/Jira-Software-questions/burndown-chart-to-show-story-points-from-sub-task-or-technical/qaq-p/130051

I completely understand your point regarding

So the graph is usually the same for a few days before it reflects the work. We would however like a daily feedback on how much progress has been made, i.e. how many/big subtasks have been closed.

I would suggest you to read the answer here from @Jack Brickey

https://community.atlassian.com/t5/Jira-Software-questions/how-do-I-track-burn-down-using-sub-tasks-where-the-top-level-is/qaq-p/692189

From the docs

The Burndown Chart is based on the Tracking Statistic. If you are using Story Points as your Tracking Statistic, then the Burndown Chart shows the Story Points per story (i.e. stories burning down the Estimate Statistic are only burnt down on the graph as they are completed); whereas if you choose the Time-tracking option, you are shown partial burndown (i.e. the number of hours currently used and remaining each day).

https://confluence.atlassian.com/jirasoftwareserver0712/configuring-estimation-and-tracking-959314838.html

https://community.atlassian.com/t5/Jira-questions/Estimation-vs-tracking-Story-or-Sub-Task/qaq-p/673114

https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html#Configuringestimationandtracking-Settingestimationstatisticandtimetracking

Like mirelm likes this

Thank you!! I read a lot of posts on the forum for a complete week and felt like I hit a dead end. I will go through the posts, hopefully it will give me some new insights.

0 votes

Jira does not support burning on sub-tasks, because it shouldn't happen in Scrum.

In a scrum, you commit to doing a set of stories in a sprint.  You burn down when the stories are done - there is no in-between - a story is either done or it is not.  So the estimates on the sub-tasks are irrelevant.

(This is not to say a sub-task burn-down wouldn't be useful to some of us as a not-really-a-burn-down-chart.  But Jira doesn't support it)

I know this and from developer's standpoint this is fine. But Product Owner and Product Manager does not always agree. There is a need to report upwards and to customers hence the need for daily burn down. So this is why we are looking into it..

Hi @mirelm,

Try our Great Gadgets app. It includes sprint / release burndown chart gadgets that can calculate by time remaining & time spent, original time estimate, issue count, story points or custom field. Also, it offers an option to include subtasks. 

For more details, please read 7Tracking an agile project that uses time estimates with Great Gadgets for Jira .

SprintBurndownByTimeRemainingTimeSpent1.png

Danut 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

83 views 1 12
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