Status: Gathering Impact (View Workflow)
Affects Version/s: 7.6.9, 8.2.3, 7.13.6
Fix Version/s: None
Introduced in Version:7.06
Support reference count:6
Symptom Severity:Severity 2 - Major
Bug Fix Policy:
Certain JQL functions can trigger a ClauseTooComplexSearchException if too many search results are returned when using the functions, including (but not limited to):
- closedSprints() - JSWSERVER-20283
By default, Jira is configured with a limit of up to 65000 search clauses - if the function will return more than this number of issues, the exception will be thrown. This is true even if the overall JQL query will not return less than 65000 issues; for example, the overall query can be constrained with a term such as (issuekey = TEST-123), which should only return 1 issue, and it will still fail.
Tested in Jira 7.6.9 and Jira 7.13.6
- Create at least 65000 issues which have worklog entries. The Data Generator for Jira is effective for creating these issues, but should never be used in a Production environment.
- Re-index the environment as needed to ensure that all issues are searchable
- Perform a query that uses the affected function (i.e. worklogDate < now()) so that over 65000 issues will be returned.
The search succeeds, and the full result set is returned.
The below exception is thrown in the atlassian-jira.log file:
The following error is shown in the UI, and the search does not return any values:
An unknown error occurred while trying to perform a search.
This is very similar, or identical, to JSWSERVER-16401 : Having a huge set of versions causes Boards to break, which is the same problem when using fixVersion.
It is possible to work around this issue by increasing the number of allowable clauses used in searches.
- Not recommended. Increase the default limit of 65000, but it is not known how this will affect future performance of the system. This can be done by increasing the value for jira.search.maxclauses in jira-application.properties file located in following directory: