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.
