I have my backlog estimated in days rather than story points. I have created sub-tasks from my stories in days too. I have configured my board to use "original Time Estimate" as the estimation statistic and have set "Remaining Estimate and Time Spent" for time tracking.
My problem: In a sprint, when looking at the burndown chart, the "Remaining Time Estimate" on the left hand side is an aggregrate of the story plus all of the sub-tasks. This is misleading in our workflow because the story estimate is our initial estimate, whereas the sub-tasks are our actual estimates. By adding these two together, the amount of work to be done is extremely inflated.
This doesn't appear to be a problem if the backlog estimates are in story points.
Also, if I set time tracking to "none", the remaining Time Estimate becomes our original backlog estimates (which is OK), however we don't see any progress on the burndown chart until the entire story is complete. I'd rather see progress as sub-tasks are completed.
My question: Is there any way I can configure my board such that the Remaining time estimate in the burndown chart is my original story estimate from the backlog but have the burndown reflect progress as sub-tasks get completed?
Thanks very much,
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs