Not using Projects in my JQL causes "Too many Issues are trying to load" in Kanban in Cloud

[Larry Wilson]

So is there a way to say projects = (all) ?

I have a query that is looking for all Issues from a given Team and the Team works across many Projects, and due to the way our company manages Projects, the list may change. Whether or not I list Projects the query shows the a small number of Issues, but when no project is in the filter the Kanban Board dies with "Too many Issues are trying to load".

It is the Cloud Jira Instance.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Yes, you already found it - don't include a "projects in (x, y, z)" clause.  This will select all projects, and I suspect that's why you are hitting "too many issues", it is looking at all the issues in the system.

You might want to give us your search so we can explain it more (obscuring data if you want - rather than name your projects, say "in (x, y, z)" like I did).  Or try it in the issue navigator to see how many issues it is returning.

[Larry Wilson]

I tried to do simply  -  status in ("Team Test")  which has only 136 issues, but the board still dies

[Nic Brough -Adaptavist-]

Ok, so you're seeing 136 issues when running that in the issue navigator, but a dying board when that filter is selected for the board filter?  (Not swimlane/colour/kanban-done/quickfilter, just the board's core filter)

[Larry Wilson]

Yes. The board itself.

[Nic Brough -Adaptavist-]

Ok, I think we need to see your full query (the working one with the project clause)

[Larry Wilson]

just add in project = SS and status in ("Team Test") ; which would only show those for the SS project, ...

Think I found a solution, ... "category in (Project) AND " ...

the Category pulls in all Projects ...

[Nic Brough -Adaptavist-]

Ok, that is what I thought - "status in team test" is reading every issue, and even though the result is only 136 issues, the board is not going to cope with everything.

Limiting it by project, or category by project reduces the context down to a size the board believes it can cope with.

[Larry Wilson]

Ok, so I have the exact same Filter Query in separate Kanban and one fails with "too many issues..." and the other works fine ... sigh

category in (Project) AND (assignee = 62e93a1296eb272011a7ccda OR "QA Assignee[User Picker (single user)]" = 62e93a1296eb272011a7ccda) ORDER BY Rank ASC

[Larry Wilson]

Works in Scrum board ... not Kanban ... 

[Larry Wilson]

To be perfectly clear, I opened a Teams Kanban, using the above filter, it works.

Tried to reuse same filter for a Project Kanban and it fails.

[Larry Wilson]

Yep, So turns out the "Powers that be" ran an across the board (literally) change for Kanban sub-filter  which caused the issue above. 

Why don't admins use a Developer Instance to roll out these issues and alert any board owners if their board is adversely affected?

Might be nice if Atlassian had a Metric showing "broken" boards with otherwise well behaved filters.

[Nic Brough -Adaptavist-]

Good question - you'll need to ask your admins why they didn't test it!