Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sprint statistic wrong

Hello community,

we have an issue added to "Sprint #7" which was completed on 08/06/2021. The issue was closed (Resolution = Done) on 02/06/2021.issue_closed.jpg

issue_sprint.jpgThis issue is now listed in section "Issues completed outside of this sprint" and the story points are not added to this sprint. issue_list.jpg

Is there an error in our database? How can I figure out why the issue is not listed under "Completed Issues" in this sprint?


1 answer

0 votes

Is "issue solved" in the last column of the board the sprint was created for?

No, in the last column is "Done".


I think we have some database errors (see Missing details in issue history log ( and also we could have errors with sprint statistics.

I can't figure out in which table of the database something is wrong.

Do you have an idea in which table could be an error or missing entries?

I don't think there's anything wrong with your database

The issue status is "issue solved", so it is not "done" (because "issue solved" is not in the last column, it's not done) and hence won't contribute towards the done count.

In the last column there is status "Done". The Ticket #2539 was changed from "Issue resolved" to "Done" on 02/06/2021. So, this are  6 days before sprint ends.

On 11/05/2021 this ticket was added to the sprint before it starts.

So in my opinion the ticket should be counted in Sprint #7 as completed?!

Am I not right?

You said the issue was in "issue solved".  Is it in Done or Issue solved now?

Look to the picture at the beginning. We changed it from "Issue solved" to "Done", the last state of the issue.

News: I reindexed Jira 3 times now. After the 3rd reindex there were no errors now and da scrum board looks different. The count of completed issues per sprint are now increased and seems correct.

Was this the workaround/fix?

Sort of, but the real fix would be to fix whatever it was that corrupted your index!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

83 views 1 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you