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:
Thoughts????
Thanks all,
Steve Josue
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.
More details in these articles:
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.