You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
what field is required (from the drop down) to trigger the burndown for remaining hours?
I have searched and can't figure it out....yes sure story points (SP) shows but that doesn't help bc SP are only closed once the epics are done.
Showing a burn down in story points is not useful for managing development.
The link provided above says that the time based burn down shows the original estimate less the time used. This idea is from the 1900's - it is the equivalent to determining how close your are getting to your office in your morning commute based on the number of minutes you have been driving instead of based on your actual location and remaining distance to the office.
I need to be able to estimate in story points and have a burn down chart that shows REMAINING TIME.
The field required should be "Remaining" not "Original".
The "Original" value should not change, as it's the team's estimate.
When hours are logged, the "Remaining" value is reduced, not "Original" (which is correct) so a burn down for "Remaining" is required.
This article explains how to do it:
Welcome to Atlassian Community!
You must be estimating your stories with time tracking fields instead of Story points to display the information in the Burndown Chart.
The field that should be selected to change the burndown Chart to display hours instead of Story Points is the Original Time Estimate:
If it's not properly appearing to you, you must activate the Time Tracking feature for your site and configure the field for your Stories, as described in the documentation below:
Let me know if this information helps.
I also turned on everything and this option is still not available. How come no one at Atlassian has learned that hiding options/actions (unless it is critical to keep it a secret) is the worst possible user experience?