Shared Sprints between Projects don't migrate successfully when sprints end and new ones start

[Jimmy Kim]

Our company is using a shared sprint across all projects in Jira.

I am noticing an issue that when a sprint ends and a new one starts that only the open tickets that fall under the project where the shared sprint is stored are migrating over successfully to the next sprint when the sprint ends. The tickets that do not fall in the project where the shared sprint is stored lose their Sprint tag altogether or are automatically moved to Backlog status.

The only workaround for this if the teams do not want a share the same sprint cycle in a project is to have the same sprint live in each separate project and start and end them at the same time. Is there a way to not have to go this route if we just want to use one shared sprint cycle across multiple projects?

[John C]

Hi Jimmy.  I've worked on projects with shared sprints as you describe before but have only run into this issue is when completing the Sprint and not changing the option for what to do with the Open/Incomplete Issues.  I think it defaults to send incomplete issues to Backlog on Data Center, and to the next Sprint on Cloud.  I take it that option is being set based on what you intend? Cheers.