Burndown chart


According to this document configuring-estimation-and-tracking, burn down chart  only can choose either story point or time spend.

My question is why not both ?




1 answer

This is for flexibility. The admins have the ability to choose either of the two, choosing both will render the gadget useless. How will the chart show a burndown guideline? Sum up the Story Points + Total Estimated Time? At the end of the day, you will be looking at your chart and say "All my stories are closed, why is my burndown chart not showing correctly? Oh that's why! Some developers have not used all the estimated hours!". 

In your suggestion, for one Story to be completely "burned down" in the chart is to use all its hours (logged hours) and close the issue? That's double effort.

I think and this configuration choice makes a lot of sense for most of the organization that we support.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 16, 2018 in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

79 views 0 4
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you