burndown chart with remaining hours not story points

[Agile Coach]

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.

Thank you

[Sowjanya Prattipati]

How does burndown with Original estimate makes sense. It should be with remaining hrs. That is the basic functionality anyone would as for a sprint tracking. I don't know how Jira could miss it.

[Daniel Kuhlwein]

You have to go into your board settings and then under "Estimation" there is an option to select "Original Time Estimate" instead of "Story Points"

[Daniel Kuhlwein]

[Richard White]

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:

https://support.atlassian.com/jira-software-cloud/docs/configure-estimation-and-tracking/

[Kirby Glad]

I think this answer misses the point.  He wants to size in point, and show the burn down using hours.  That is what I want too. 

[Petter Gonçalves]

Hello,

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:

Configuring Time Tracking

Let me know if this information helps.

[Pablo Osorio da Silva]

Actually I got a similar issue, at this moment I can't track "Remaining Time" on Burndown chart.

[andrew]

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?