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?
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. :-)
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?
I altered the end date of the sprint before closing the sprint.
Thinking about it, I closed all of the issues yesterday and assigned them a fixVersion. I also closed the sprint yesterday, although the date for the sprint end was set as 2 days ago (i.e. a day before I closed the issues).
This would logically be the problem.
Can I change the sprint end date within Greenhopper, or can I only change it via the DB?
Or I suppose I could alter the closed date of the issues?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs