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

Sprint Report - Issues Not Complete

Steve Sweales

I have just closed off virtually all of my stories within a sprint by assigning a fixVersion, then marking the stories as Closed, then marking the sprint as complete (a couple of days later than planned - not sure if that is the cause of my issue).

When I look at the sprint report, specifically the Issues Not Completed section. All of my stories are located within this section, whereas it should be about 50 odd are completed and only 2 are not completed.

It states against all of the stories that their statuses are Done (a step before closed in my workflow) which is incorrect. However if I look in the issue navigator, they all have the correct status of Closed.

I'm confused - why is the Sprint Report incorrectly showing all of the stories as incomplete?

Accepted answers

Steve Sweales

Th problem turned out to be that I had my final closed status 'Done Done' outside of Greenhopper (so that team members could not transition something to that status).

This meant that issues were never truely complete. By moving the status into Greenhopper (and restricting it by the workflow), the items were magincally marked as complete. :-)

All comments

codelab expert

The first time I was wondered too :-) The sprint report is frozen to the last date of your sprint. Any changes after this date are NOT included in this report. When you close your issues after the end date of your sprint then they still remain incomplete in sprint report. I suggest this is a workaround because you can't currently get history data using JQL.

Steve Sweales

Just to clarify, are you are saying that ...

My sprint took 12 days instead of the originally planned 10, and as I closed the issues then the sprint on the 12th day, as it was 2 days past the original date, this is why they are marked as incomplete. If I had closed everything on the 10th day, then they would be marked as complete?

codelab expert

Yes, this is right. On the other hand you can change the end date of the sprint (2 days later). The report is focused on this parameters (begin and end date of sprint).

Steve Sweales

Can I do that after the sprint has been closed?

Steve Sweales

Th problem turned out to be that I had my final closed status 'Done Done' outside of Greenhopper (so that team members could not transition something to that status).

This meant that issues were never truely complete. By moving the status into Greenhopper (and restricting it by the workflow), the items were magincally marked as complete. :-)

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