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

Burndown shows no issues completed when the sprint is closed

David Taylor13

Our Burndown chart shows issues completed as we work in the sprint, however when we close the sprint at the end, the redline becomes flat, and no issues are showed as completed. Only any issues that were not completed show in the reports. The other charts such as the velicity chart display the same behaviour.

A couple of examples are below. The firrst image is a closed sprint, the second is the current sprint in progress. As you can see from the in progress sprint, everything looks fine. However when we close it, it will end up looking like the first one.

FYI: Our "Done" comlumn in our sprint board is "Closed" status.

Accepted answers

David Taylor13

Atlassian narrowed it down to our query for the main board. Below is the explanation

When the planning board is viewed, it will automatically exclude the 'Done' column so it doesn't need the filter to have those statuses removed. If you filter out those statuses it will break the chart calculations as it will not return those issues.

See GHS-10855 for more details.

All comments

Luther Hargrove

I would first make sure that a resolution is being set on those issues. If no resolution is set, it can be 'closed' but appear to be still open.

David Taylor13

I checked and the resolution is being set.

There is a transition event from "In QA" to "Closed" which is "The Resolution of the issue will be set to Completed."

David Taylor13

Atlassian narrowed it down to our query for the main board. Below is the explanation

See GHS-10855 for more details.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration