Issue with Burndown Chart where time logged is not getting captured

Prathyusha Gottu

We are trying to use the Burndown Chart

We started sprint yesterday, but the time spend graph is not updating so we started looking at each jiras and noticed few issues. 

 

B4-381 has 1 day remaining but developer logged 1 day time against it which was not showing up in the graph. Remaining stayed 1 day but 1 day was spent on it. See attached images. 

 

Even though developers are logging time the graph stayed mostly flat.

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

There's a couple of problems here. 

First, it's a burn-down chart, which means it measures burn, not logging.  You only burn when an issue is done, not while it is being worked on.

Second, the lines look rather flat because your hours are so high - it's just not able to show you the variance because it's just not got the resolution to do it.  Scrum isn't intended to be done this way either - the maximum hours for a 2-week sprint in a large Scrum team would be 560, but even that's too high because it ignores overhead like meetings and planning, a realistic number is a bit under 500.