-
Type:
Suggestion
-
Resolution: Timed out
-
0
-
3
Problem
On Jira Cloud Kanban Boards, there is currently a 5,000 issue limit when trying to render the board. The board will fail to load if the filter query returns more than the limit and the error message will ask the user to check their filter query to see if things can be narrowed down.
However, if the error is thrown and a user tries to use a Quick Filter on the board page, the board will continue to fail to load complaining about the Issue limit being breached.
When clicking on a Quick Filter, it seems that the main filter query is still run and THEN the quick filter query is run right after that. Since the board fails to load on the first query, the Quick Filter is rendered useless in any attempts to narrow down the results displayed on the Kanban board.
Steps to Reproduce
- Create a Kanban Board in Jira and create a filter query that potentially returns more than 5,000 issues.
- Try to access the Kanban board and let it error out.
- Attempt to click on a Quick Filter for a given user. The default quick filter of "assignee = currentUser()" is fine.
Actual Results
- Clicking on the Quick Filter does not change anything. The board still fails to load, complaining that the limit of Issues has been breached.
Expected Results
- Clicking on a Quick Filter to just view, say, only the tickets assigned to a user should render the Kanban Board with the smaller result set.
Suggestion
It appears that currently, when we click a Quick Filter on a board, the main filter query runs, followed by another query that includes the extra parameters to narrow down the search. The failure of the main query seems to adversely affect any subsequent queries. To avoid this, would it be possible to change the Quick Filter so that it only runs the query that will produce a reduced result set?