-
Bug
-
Resolution: Fixed
-
Low
-
7.7.0, 7.6.2, 7.12.3
-
7.06
-
1
-
Severity 3 - Minor
-
Problem
While converting JQL query to Lucene query Jira tries to guess projects to which the results will belong. This enables Jira to perform some optimisations. For example:
- Optimised security qeury
- version functions are expanded to versions from only related projects.
Unfortunately, those guessed projects are not passed into subqueries.
The problem reveals itself on Kanban board with default Kanban sub-filter:
fixVersion in unreleasedVersions() OR fixVersion is EMPTY
Test case
- Create 2 Kanban projects
- Create 33k unreleased versions for each project (66k in total)
- Try opening Kanban board
Expected result
Everything works. Lucene query contains 33k versions from current project. (optimization worked and sub-filter receives the project scope)
Actual result
Jira tries to create Lucene query with 66k versions from the whole instance. (Optimization failed)
It also fails due to BooleanQuery limit.
Workaround
Removing 'OR fixVersion is EMPTY' fixes the optimisation.
- causes
-
JSWSERVER-13194 UnreleasedVersions() is slow on large instances
- Closed
-
JSWSERVER-16401 Having a huge set of versions causes Boards to break
- Closed
- has a regression in
-
JRASERVER-69936 Regression in queries with large list of projects
- Closed
- relates to
-
JSWSERVER-10971 Optimise default work query for boards.
- Closed
- duplicates
-
JSEV-2580 Loading...