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.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot