Sprints are tied together across Projects but should not be, how can we change this?

[Gabrielle Chapman]

Hello,

We are having an issue where two sprints under two separate projects are somehow linking together. If I change the name of the second, inactive sprint on board B it will de-activate and re-name the current ACTIVE sprint on board A. Then if I re-activate the sprint on sprint A and re-name to the correct name, the second and inactive sprint on board B activates and re-names.

Board A is attached to different projects than board B. Anyone have an idea??

Gabrielle

[Bill Sheboy]

Hi @Gabrielle Chapman  -- Welcome to the Atlassian Community!

I can think of a couple of scenarios which might cause this behavior...

1. The filters of the two boards for the projects overlap somehow (e.g. multiple projects) before the sprints were created
2. An issue was moved from one project to another when a sprint was active.  There is a suggestion to make this visible before a move breaks things: https://jira.atlassian.com/browse/JSWCLOUD-11992

For scenario 1, check your board filters to confirm that they are distinct for the projects.  You can find those under the ... menu > Board Settings > General > Filter.  If they overlap, correct that and then address the sprints in the projects.

For scenario 2, one or more issues moved to a new project with a active sprint value already assigned.  If you can identify the issue(s), you can:

• Remove it from a sprint
• Use bulk edit to clear the sprint field
• Re-add it to the correct sprint

Best regards,

Bill