JQL for Unassigned Tickets in future sprint

[Evan Giordanella]

I have one project with multiple boards where each board shares the same backlog. The following SQL is used to filter per board:

Board 1
project = XX AND "Team[Team]" = 40 OR project = XX AND assignee is EMPTY OR project = XX AND issuetype in (Bug, Incident) ORDER BY Rank ASC

Board 2
project = XX AND "Team[Team]" = 50 OR project = XX AND assignee is EMPTY OR project = XX AND issuetype in (Bug, Incident) ORDER BY Rank ASC

Each board creates multiple upcoming sprints for planning. However, with the current filter, the moment an unassigned ticket gets moved into Board 1's future sprint, that sprint is visible on Board 2 as well.  

I am wondering if there is a way with JQL to have all tickets in future sprints, even if unassigned, will only show up on the board in which the sprint was created? This will prevent sprints from showing up on other boards unnecessarily.

[Nic Brough -Adaptavist-]

A sprint will appear in a board if there is an issue in the sprint that is selected by the board.

Your two boards both select for your unassigned issue, so when it goes into the sprint created in board 1, it causes the sprint to be shown in board 2.

>I am wondering if there is a way with JQL to have all tickets in future sprints, even if unassigned, will only show up on the board in which the sprint was created?

The only way to do that would be to separate the board selections completely, making them so they can not select the same issues.

[Evan Giordanella]

Is there no way to say: backlog shows everything but the moment a ticket is in a given board's sprint (future, or open) not not see it on any other board for that same project?

[Nic Brough -Adaptavist-]

No, because the boards select issues they should see.

You could add "and sprint is empty" to a board filter, but this does mean you won't be able to use the board as a Scrum board any more, because it will never display issues as cards on the board.