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

Release Burn-Down chart story points shows remaining story points

Lander Albrecht

The release burndown chart keeps going on because 2 story points are not completed.

However, every issue regarding that particular release/fixversion has the status closed. The issues are closed in the respective sprint and the fixversion has been released.

Could anybody help me to figure out why there are 2 story points left or tell me where to find the issues.

Accepted answers

All comments

Nic Brough -Adaptavist-

Are all your issues (and their sub-tasks if they have any) in the last column on the board when you end the sprint?

Lander Albrecht

When I execute en JQL query to list all issues related to that specific version everything is closed (=last column)

Lander Albrecht

Nic Brough -Adaptavist-

That graph tells us nothing. What does your board say is in the last column? More importantly, what does your board say is NOT in the last column, and what is the board config? (Does it map every possible status for the board filter?)

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

board

burndown

release