List of jiras showing false status on sprint reports for closed sprints.

Kishore D_suzx08

We had some activity happen around August  for our jira Datacentre. (migrated from on-prem to AWS cloud). we have seen some issue for sprint reports in one of the project.

Sprint reports which were completed inAugust and before august are showing false status on sprint reports. But for current sprints it showing correct result.

For older sprints, complete list of jiras in that project showing as INPROGRESS where as all jiras are CLOSED before closing the sprint.

Any help on why this issue? and what can be done to fix this issue?

Nic Brough -Adaptavist-

A diagnostic question - where are these issues "showing as <status>"?

I assume by "complete list of issues", you mean you have run a search for the issues and they are showing "In progress" in the status column in the issue navigator.  Is that right?

If it is, then can you pick one of the issues that you think should be closed, and go into the full issue view.  What does the status show as in there?

If it is showing "closed" in the issue view and in-progress in the issue navigator, then there's a simple answer - your index is corrupt.

The easy fix for a corrupt index is to run a full locking re-index.  But you should also try to work out why it's been broken, in case there's something that's going to continue to corrupt it.  (A migration between servers can cause it if it is done badly, but it's a one-off - running a migrated system won't cause more corruption).  At least put a reminder into your calendar to check for any corruption regularly, after you've re-indexed.

If the issue navigator matches the issue view, then you have a different problem.  I would look at the issue history to check who changed the status, and examine why you think issues that are in the status in-progress should be closed.