Sprint Report - Issues completed outside of this sprint

[Grzegorz Reglinski]

In Sprint Report is section named "Issues completed outside of this sprint". What is the rule for the tasks there display?

[Nic Brough -Adaptavist- · Accepted solution]

It's issues that match the board filter that were not in the sprint, but moved to "done" outside the time the sprint was running.

[Pablo Ziliani]

Is it? inspecting the changelog of a couple of issues in that section shows that they both were

1. added to the sprint, and
2. marked as resolved

before the sprint had even started. The resolution date is earlier than the sprint start date.

[Barry DeJaeger]

Thanks Nic, I noticed that these tickets don't seem to be reflected in the chart on the report. Is there a way to fix that and have them included in the chart and included in the sprint? In the case where it was meant to be in the sprint but was accidentally not moved into it?

[Nic Brough -Adaptavist-]

No, because they weren't in the sprint - the board can only report on things that were.

[Romualdas Laurinavičius]

@Barry DeJaeger I see your post is very old, but in case someone else is looking for a workaround, here is what you can do (this is JIRA Cloud):

1. Enable parallel sprints in JIRA settings
2. Reopen the closed sprint that is missing the tickets
3. Once the sprint is reopened, go to the issues you want to be included in the sprint, make sure correct sprint is assigned, move the tickets out of Done and then back to Done, so that new Done time is recorded
4. Complete sprint
5. The tickets should now appear in the sprint report where you want them
6. Disable parellel sprints in JIRA settings

Hope this helps.

[Alexey Pavlenko _App Developer_]

For those who are looking for the solution of the problem and open to paid options - you can use the the app I have developed - Multi-team Scrum Metrics & Retrospective. I handled this and several other problems/limitations there (the inability to include removed issues from a sprint to uncompleted scope (while many engineers remove issues manually from a sprint); the inability to exclude duplicated issues (for example, from 'Issues Not Completed'), etc.).

Best regards,
Alexey

[Srikanth_Reddy]

I notice the same issue in my previous sprint too after closing sprint board. And the velocity report shows incorrectly even we finish the committed job. What is the solution to this, how can I make changes to the closed stories or the story points, those are reflecting as carryover points? 

[Pablo Ziliani]

This seems to be a duplicate, here's the accepted answer: https://answers.atlassian.com/questions/39231597