Why would labels in a JQL make it too complicated for a scrum board?

[Jeramy]

I'm using a JQL for a scrum board.

The JQL is:

(project = "<project name>" AND issuetype not in (Test, Sub-Task) AND status not in ("Needs CS Input", Triage) AND (component != RP or component is EMPTY)) or labels in (<LabelA>,<LabelB>) ORDER BY Rank ASC

Why does the label clause make this JQL too complicated for my Scrum Board? When I look at the Scrum Board's configuration, I see:

Projects in board: The projects in this board cannot be listed because of the complexity of the board filter

No matter which way I try to rewrite the JQL, the labels part makes it too complicated.

What am I missing? 

Thank you!

[Kian Stack Mumo Systems · Accepted solution]

@Jeramy, 

That is because labels are a global object and could potentially return tickets from any project.

Are you trying to only return tickets from the project in the initial part of the query?

Thanks,

Kian

[Jeramy]

@Kian Stack Mumo Systems  - Thank you for the quick response.

My actual issue that I'm running into is a scrum master lost the ability to close/start sprints. I've looked at their project and she has the Manage Sprints, Edit Sprints, and Start/Complete Sprints permissions. Knowing that she needs all of those permissions in all projects associated with the board (indirectly the sprint), I was using the board to try and find other projects that I need to look at. As I was typing this, I realized that I can just use the JQL itself and look for Labels in (LabelA, LabelB) and it will return what I need. 

Thank you for the great response!