How can I prevent colliding linked sprints across two projects?

Question

This question from 2018 explains the issue pretty well. Two sprints end up somehow linked in a way that one being active prevents the other one from starting. Last time, I followed the directions to label tasks and recreate both sprints, but that's not sustainable.

There are two projects: A and B.

The board for team B is just project B.

The board for team A is defined as A and B.

The leader of team A claims that it works fine if the sprints are started in a certain order. They claim that the only problem is that the leader of team B started the sprints in the wrong order.

I can't find any evidence that this should work at all, and I can't keep cleaning it up for them. The person who supposedly set this up has left the company.

Is this even something that should hypothetically work, or do I need to tell team A to take project B off their board definition?

Mikael Sandberg · Answer

You can always check the history if an issue and see when and who added the sprint to the issue that is causing problems. I would also check the filters on the boards, I have had teams the made the filters so broad that they spanned all our projects because it was basically just labels = something and nothing else.

Casey Gould · Answer

Thanks, Mikael. If the answer is that it hypothetically could work, I think the problem I'm left with is the finger pointing on who's doing what wrong.

Casey Gould · Answer

Your answer to the title seems to be "You can't," but I don't believe you've answered my core questions about the scenario.

Unfortunately, I need something stronger to push for permanently untangling the boards, and the leader of team A is adamant that everything was perfectly fine until some manual process (undocumented, of course) wasn't followed.