Issue Closed in a Later Sprint Appears as Completed in an Earlier Sprint (Sprint Reports)

Question

Hello everyone,

I’m facing an issue with Jira Sprint Reports and would like your help to resolve it.

Here's the situation for example: I have a task that was created in Sprint 2 but wasn’t completed within that sprint. The task was then moved to Sprint 3, and it was closed in Sprint 3. However, when I check the Sprint Reports, the task appears as completed in both Sprint 2 and Sprint 3.

From my understanding, if a task isn’t completed in the original sprint (Sprint 2), it should be reflected as incomplete there and only show as completed in the sprint where it was actually closed (Sprint 3). But it seems to be marked as completed in Sprint 2 as well, which affects the accuracy of my reports.

I’ve tried different methods to pull accurate sprint data, such as using JQL queries and checking resolved dates, but I still see the same behavior in the Sprint Reports.

Is this an expected behavior in Jira, or is there a way to fix this so that a task is only marked as completed in the sprint where it was actually closed?  What I want is to accurately find and report the completion rates of issues in past sprints.

I would really appreciate any advice or solutions.

Thanks in advance!

Alexey Pavlenko _App Developer_ · Answer

Hi @Emre Can Şahan ,

I don't encounter such an issue.

* Add task-1 to Sprint 1.
* Start Sprint 1.
* Complete Sprint 1 and move task-1 to Sprint 2 since it wasn't completed.
* Start Sprint 2.
* Open Sprint Report for Sprint 1. Task-1 is in "Issues Not Completed" section.

The Sprint Report definitely has several issues, such as removed issues from a sprint cannot be considiered as an uncompleted ones (while many engineers remove issues manually from a sprint), and the inability to exclude duplicated issues (for example, from 'Issues Not Completed'). Additionally, it's impossible to see tasks that were completed outside of a sprint if those tasks weren't ultimately added to the sprint. I am the developer of the app that solves all these problems, but the issue you describe is not the problem the Sprint Report has.

Best regards,
Alexey

Dick · Answer

Hi @Emre Can Şahan Welcome to the Atlassian Community

You can edit the sprints field holding the consecutive sprints that a ticket was in to avoid having it being completed in all the sprints listed there.

Hope this work-around can help you,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)