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
