Incomplete issues not rolling over to the next sprint

[Nicole Russo]

We have a problem that I haven't experienced in JIRA before.  In my new team, we have a big set of teams and quite a lot of issues that are incomplete at the end of the sprint and need to roll over to the next sprint.

When the sprint is closed each fortnight, we always select to roll open issues to the next sprint, but every time at least half of the issues end up in the backlog. It's very frustrating, the issues that get backlogged seem to be random, and we have to go back and find the missing issues.

Could it be related to the number of issues being rolled over? Anyone else experienced this? We're using JIRA cloud.

[Bill Sheboy]

Hi @Nicole Russo 

Have you already resolved this issue?  If not...

When you are closing the sprint and rolling open work items over, have you already started the new sprint?  If so, that would explain why *all* rolled over items go to the backlog.  But it would not explain why only some of them do so.

Update: I just read another post about this symptom... for projects with multiple boards, work is shared across boards, and the sprint is closed on one board, items get split going to the next sprint or the backlog.  Are you using multiple boards for a project?  If so, I would suggest submitting this issue as a defect to support.

Best regards,

Bill