Another sprint shows up on a board, possibly due to filter?

[Greg Williams]

Forgive if this is already covered...

We have a project with multiple boards, all Scrum.

One particular Scrum board (Board A) is searching for all tickets in the project and that's it.  It's showing Sprints from A and B in the backlog.

Another Scrum (Board B) is searching for all tickets with a component value to narrow the tickets down. That board's Sprint is the only one in the backlog.

So Board A JQL is changed to:
project = <PROJECTNAME> and component = "COMPONENT A" ORDER BY Rank ASC

And Board B JQL remains:
project = <PROJECTNAME> and component = "COMPONENT B" ORDER BY Rank ASC

Then the other board's Sprints should not be crossing over to another board?

[Trudy Claspill · Accepted solution]

Hello @Greg Williams 

A sprint displays on a board when the sprint contains an issue that is within the scope of the board.

If a sprint you create in Board B gets an issue assigned to it that has the value COMPONENT A set in it, then that sprint will show on Board A.

It doesn't matter in which board the sprint was created. It only matters if the sprint contains an issue within the scope of the board you are viewing.

[Mikael Sandberg]

Sprints are not project or board specific and can be used on any issue no matter the project. So it sounds like someone picked the wrong sprint when assigning an issue to it. I always recommend that your assign issues to a sprint from the backlog on the board, that way you know that it will only be assigned to one of the sprints on that board.