Closing My Team's Sprint Silently Closes a Related Team's Different Sprint

[Alex Wilson (TMNA)]

Over the past 2 or 3 Sprints when I Close my Sprint everything seems to work fine ..... except that another sprint for one of our other teams gets closed "by me" too.  Nothing I see indicates that this going to occur .... or has occurred.   However, when we look at the other sprint it says "Closed By ... my name"!  We have always been able to "Reopen" the Sprint closed accidentally.

Sometimes only the "other" sprint closes.  Other times both my sprint and the other sprint both close.  And sometimes only my sprint closes, the expected case.

I'd love to see a list of things to check into that could be causing this!!  Somehow our two Teams are a bit "Too Close".

We do have some "common" stories that display on both Boards, but not a huge number. 

[Mikael Sandberg · Accepted solution]

Hi @Alex Wilson (TMNA),

Welcome to Atlassian Community!

Sprints are not board specific, and this happens if one or more issues on your board has been associated with a sprint on another board. Usually this happens if users are assigning the sprint directly from within the issue instead of using the backlog to assign issue to a sprint.

I always recommend that you move issues into sprints from the backlog, that way you can avoid this from happening. 

[Alex Wilson (TMNA)]

Thank you.

[Michael Yaroshefsky - Visor for Jira · Accepted solution]

Hey @Alex Wilson (TMNA) as Mikael and Manoj have said the most likely cause of this is shared issues between the sprint you meant to close, and the sprint that was closed unintentionally. 

This thread has more detail that should help you diagnose and troubleshoot the problem:

https://community.atlassian.com/t5/Jira-questions/Closing-the-spring-in-one-project-closes-the-sprint-in-another/qaq-p/2468059

This is quite a common problem people encounter, as Manoj and Mikael say it's typically only avoided by keeping your processes a bit more rigid. 

Hope that helps!

[Alex Wilson (TMNA)]

Thank You

[Manoj Gangwar · Accepted solution]

Hi @Alex Wilson (TMNA) Welcome to the community! 

The most likely causes are either shared issues between boards or overlapping board filters. Verifying that each board only pulls the issues intended for its respective sprint, and ensuring that shared stories are properly assigned, should help resolve the problem.

[Alex Wilson (TMNA)]

Thank you!

[Alex Wilson (TMNA)]

Thank you!