2 Projects, 1 board - sprint finish causing cards to move to different status

[dexter driver]

Hi, 

I have 2 projects (Proj A and Proj B). Proj A has shared sprints with Proj A and Proj B assigned to the shared sprint. 

When closing the sprint in Proj A, the selection was to move to the next sprint. 

Project A cards when to next sprint 

Project B cards when into the backlog. 

This is the 2nd time we have used the shared sprint however has only occurred on the 2nd sprint. 

Any idea why Project B cards when into backlog rather than the next sprint?

[Trudy Claspill]

Hello @dexter driver 

Welcome to the community.

Are you working with Jira Cloud or Jira Server/Data Center? If your URL is like

https://<something>.atlassian.net

...then you are using Jira Cloud.

If you are using Jira Cloud, are you working with a Company Managed project or a Team Managed project? It will say which at the bottom of the navigation pane on the left.

If you are working with Jira Server/Data Center, what version are you using?

A project is not "assigned" to a sprint. Sprints exist in the contexts of Scrum Boards. Scrum Boards use a Saved Filter to determine which issues to display on the board.

A Sprint is created within a Board. Though the Sprint is associated with a specific Board at creation, Jira allows you to put issues from any accessible project into your sprint. This could be done by editing the Sprint field of the issues not contained in the Board's Saved Filter.

While a Sprint is associated to the Board in which it was created, the Sprint will display in any Board that has a Saved Filter that encompasses any of the issues in the Sprint. This can lead to confusion because you can't tell which board the sprint was created from. 

So, while you say the sprint is "shared", the question becomes

- is it shared because it was created in a board where the board's filter encompasses both projects, or

- was it created in a board specific to Project A and the sprint became shared because a Project B issue was edited to set its Sprint field?

If the latter, then Project B is not in scope of the Board's filter. When the Sprint was closed, Project B issues have no knowledge of the next sprint for that board and would've been moved into the backlog of their own board.