Time Spent not being logged properly in sprint burn down chart

Ken Ng_i5465x

We have a subtask that was given estimate of 1 day value.  On the 24th of Aug, they changed it to 2hrs since they over estimated.  While on that same day the 24th, they logged 6 hours.  Also on the 25th they also logged another 3 hours.  Why isn't the burn down charts showing the proper values of 9 hours ?

 

 

Sprint burn down chart below.....<-- NOT showing total of 9 hours spent on the subtask

 

 

Jira Work Log Audit Trail......

Nic Brough -Adaptavist-

Hi Ken,

This is failing because you do not put sprint estimates on sub-tasks - they are not sprint items, and should not have estimates.

Scrum only looks at Sprint items when drawing up the burn-down chart, and sub-tasks are fragments of sprint items, not part of a sprint themselves.

Burn-down looks only at what you commit to, and what you achieve (done, or not done), there is no partial completion - an issue with no sub-tasks done is not done, with one sub-task done, it's not done, with 99% of sub-tasks done, it's not done, it's only done when 100% of them are done.

So there's no point estimating them, they tell you nothing about whether the issue is done or not.

If you put sprint estimates on sub-tasks, the velocity chart works fine because it ignores them, but the rest of Jira goes on to double-count them, because it does not expect them to be there.

You have two options:

• Use sub-tasks as intended - as parts of sprint items.  Get rid of the estimates on them
• Create a strategy for putting them on sub-tasks, and automate how it works for Jira  (The most obvious one is "add up all the estimates on sub-tasks and add that to the parent", but that will fail, most people who try it carry on double-counting, or half counting, you have to be a bit more clever)