Burndown chart not updating

[satouysq]

Even if you register the time spent and remaining estimate , the time spent(green line) until the day after the sprint start will not be reflected in the burndown chart.The remaining estimates (red line) are reflected.
After the next day, the green line will rise.
Looking back to hear back from you guys.
Thanks in advance.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

A burn down chart is for displaying the sprint's velocity, which is a measure of completion, not time logged.  That's in the red line.

The green line is the time logged, shown as a useful convenience.  You'll notice it's almost a mirror image of the red (red is, in your case, the issues estimates - you'll note there's a couple of un-mirrored spikes where you've changed the scope of the sprint, and no-one has logged any work)

Issues estimates and time logged only get measured on a burn down chart when an issue is completed (moved to the last column on the board)

[satouysq]

Thank you for your reply.

For example, looking at the history of a AUTH SDk-496 backlog,

2022/12/21 17:06 updated the Time Spent 0M→5H
　⇒green line is not updated　※
2022/12/21 17:06 updated the Remaining Estimate　1D→2H30M
　⇒red line is updated（Please refer to the image）
2022/12/22 14:55 updated the Time Spent 5H→1D1H30M(1D=7.5H,Spent 4H)
　⇒green line is updated（Please refer to the image）

I want to know why the green line is not updated in ※

[Nic Brough -Adaptavist-]

None of your updates to that issue have closed it.  So there's nothing to burn down on.

[Ste Wright]

Hi @satouysq 

Just to confirm what is happening:

1. This is a chart based a Sprint
2. The red line is reducing pre-Sprint when changing the Remaining Estimate
3. The green line is staying flat when logging Time Spent until the Sprint starts

^ If yes, as far as I know, this logic is correct - this is because:

• The Remaining Estimate will change the red line, because it's reflecting the actual current size of the Sprint - which can be changed before it starts
• The green line however only visualises work down within the Sprint itself - so anything done before or after the Sprint is not counted

Ste

[satouysq]

Thank you for your reply.
The chronological order is as follows.

2022/12/21 15:42 Sprint start　(Sprint5)

For example, looking at the history of a backlog,
2022/12/21 13:22 updated the Sprint　None→Sprint5
2022/12/21 17:05 changed the Status　TO DO→IN PROGRESS
2022/12/21 17:06 updated the Time Spent 0M→5H
2022/12/21 17:06 updated the Remaining Estimate　1D→2H30M

However, in the Burndown Chart table, there is 2022/12/21 17:06 RTE change, but there is no Work logged. Therefore the green line does not rise.