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; } } }

In the release burndown chart, points added to a sprint do not match the previous reporting period.

Jennifer Trageser

I've been monitoring our release burndown for several projects and am reporting to management the scope changes every two weeks - points completed, removed and added. I've noticed that for past sprints the points added is not the same number as previously reported going back 5+ sprints. However, the points completed per sprint is always correct.

The POs cannot explain the increase in story points, the issue navigator view doesn't show an increase in story points by the team re-pointing a story or the team bringing in new work.

Any ideas on what is causing this reporting issue?

Accepted answers

Ignacio Pulgar

Maybe your board Columns setting has been recently changed. Varying status mapping to columns, or changing the columns order may impact those reports.

Also changing the board's filter may impact the reports.

All comments

Ignacio Pulgar

Maybe your board Columns setting has been recently changed. Varying status mapping to columns, or changing the columns order may impact those reports.

Also changing the board's filter may impact the reports.

Jennifer Trageser

Thanks for the info.

Ignacio Pulgar

You're welcome! Should you find this answer as helpful, may you accept it?

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

burndown

report