Multiple Sprint number tagged for completed sprint tickets or issues

[Deleted user]

The issues (stories/Bugs/Tasks) which got completed in previous sprints is showing current sprint number though it is not displayed in the 'Active Sprint' board.  

Eg :  Issue id - 12345 ;  Sprint - Sprint 8 + 3

The above issue got completed in sprint 5.

Can anyone please explain why this is happening and how to fix this problem.

Details:

We are using Company managed project

When closing the sprint moving all the items on the active sprint board to the next sprint by manually editing the sprint number and then completing the sprint (Complete Sprint).

Any ideas or thoughts is highly appreciated.

Thanks

Rekha

[Nic Brough -Adaptavist-]

The sprint field contains all the sprints the issue has been in, and the current one.  

>When closing the sprint moving all the items on the active sprint board to the next sprint by manually editing the sprint number and then completing the sprint (Complete Sprint).

Stop doing that.  It's  pointless and misrepresents what is happening in your sprints.  Just close the sprint, Jira will take your open issues into the next sprint automatically.

[G subramanyam]

Hi @[deleted] welcome to the Atlassian community.

For your query, I would suggest looking at the fields in the active Sprint stories. The likely scenario I noticed in some of my Sprints is the story/ task/ bug has been initially mapped to a upcoming Sprint number(s). If that story(s) either got cancelled or completed prior to that mapped Sprint number, then this issue happens.

So, I started exporting my Jira board issues to view the fields and the data filled-in which helped narrow down the issue.

Your scenario can fall into the similar category.

[Deleted user]

Thank you Subramanyam for you inputs. I'll definitely try the option you have suggested. But I see this issue happening on most of the tickets.  Could it be related to the way I close the sprint.

[G subramanyam]

Hi @[deleted] if that scenario,

1. My suggestion is to check the Sprint start and closure dates and time.

2. Before the start of the Sprint, how many Jira issues were available in the Sprint board and what is the count end of the Sprint?

The above two should give if any new Jira issues have been pulled once Sprint started.