Burndown completely ignoring sub-task hours using "Remaining Estimate".

Question

We are using Jira Cloud and, in the settings, we turned on "Enable Timekeeping" and the "Estimation Type = Story Points". The other symptom is we no longer have any history of
 committed story Points in the Velocity Report, only completed.  Workaround for "Remaining Estimate" burndown: If we load the sum of the sub-tasks up into the story level, and zero out the sub-tasks, the burndown works using logged time against the story. This is not what we want to do.

Some contexts:

* We have 5 other teams using same settings and their burndowns look great using Remaining Estimate burning down sub-tasks hours. When we switch to view Story Points burndown, that looks good as well. The only difference between the problematic team, is that we put a new workflow underneath it recently. Our Jira support staff doesn't think the workflow has anything to do with the failures in our reporting.

Thoughts????

Thanks all,

Steve Josue

Zane eazyBI Support · Answer

Hi, @steve_josue

If you do not mind using a third-party app, eazyBI can provide Sprint reports that include sub-tasks and allow you to see progress based on estimates and logged hours, as well as story points. eazyBI aggregates logged hours and estimates from sub-tasks based on the sprints of their parent issue.

For example, you can build a comprehensive Sprint burn-down report based on remaining estimates and logged hours that includes all sub-task data.

Check out this interactive example: https://eazybi.com/accounts/1000/cubes/Issues/reports/144076-time-tracking-burndown-in-selected-sprint

We also have several sample sprint reports that might be helpful for your team's needs in our Demo account: https://eazybi.com/accounts/1000/dashboards/5956-sprints-overview

Best,
Zane / Support@eazyBI.com

Danut M [StonikByte] · Answer

Hi @steve_josue,

Welcome to the Atlassian Community!

As far as I know, Jira's reports and gadget do not take subtasks into account.

If you really need to track by sub-tasks, my advice is to stop struggling with the Jira reports and look for a plugin on the Atlassian Marketplace that can generate better reports.

In case you consider the idea of using a plugin, our Great Gadgets app offers all you need for tracking you sprints / projects by any type of estimates (story points, remaining estimates, etc), with/without sub-tasks. The app offers gadgets like Sprint Burndown Burnup Chart, Release Burndown Burnup Chart (with Forecast), Team Velocity and many more - all you need for tracking the projects in the way you want.