nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Story Points changed before sprint but Burnup Chart reads previous Story Points

Peter McCullagh

Hi, I have found what might be a bug in the Burnup Chart point tracking which results in the Work Scope and Completed Work not being a correct representation of the sprint.

Is this a known issue?

The timestamp history of any relevant changes is as follows:

9/2/24 10:18 - Story created.

9/2/24 10:20 - Story Points set to 2.

13/2/24 - Sprint started.

21/2/24 09:14 - Story points changed from 2 to 0.

21/2/24 10:42 - Story moved into Sprint.

23/2/24 - Story completed.

27/2/24 - Sprint completed.

In the Burnup Chart, on 21/2/24 (when the story is moved into the sprint), the chart increases the Work Scope by 2.

In the Burnup Chart, on 23/2/24 (when the story is completed), the chart increases the Completed Work by 2.

Accepted answers

Mina Soultan

When the Story is moved into the sprint---> this means the "Scope of Work" increased --> that is why the chart increases the line of the "Scope of work" in red

When the Story is completed into the sprint---> this means the "Completed Work" increased ---> that is why the chart increases the line of the "Completed work" in green

All comments

Mina Soultan

When the Story is moved into the sprint---> this means the "Scope of Work" increased --> that is why the chart increases the line of the "Scope of work" in red

When the Story is completed into the sprint---> this means the "Completed Work" increased ---> that is why the chart increases the line of the "Completed work" in green

Peter McCullagh

Yeah I understand that that is how the chart is calculated but the story in the example is updated to be 0 Story Points before it is moved into the sprint yet it still increases the Work Scope and Completed Work by 2 which was the previous Story Points value before it was changed to 0 (before entering the sprint)

Mina Soultan

Hello Peter ,

I think that's because Burnup chart registers the completed story points VS the number of story points that were in the sprint backlog when the sprint was started (commitment)

Peter McCullagh

Ah yes that would make sense if it is calculated from a snapshot of the backlog when the sprint started. However, this then would cause the chart to be incorrect if stories are updated after the sprint started and stories are pulled in. The chart is now unreliable if it does not use the most up to date data for the stories in the sprint

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud