JQL queries fail due to over 65,536 sprints in Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
To search for sprints, Jira uses a terms set query. If you have more than 65,536 sprints, including closed sprints, some JQL queries on sprints may fail when using OpenSearch. In Lucene, this limitation is not present, but you may begin to experience performance concerns.
Cause
By default, OpenSearch limits the maximum number of terms in a terms query to 65,536. When there are more sprints than this limitation, JQL queries can fail.
Environment
Jira Software Data Center using OpenSearch
Solution
Adjust max terms in OpenSearch
In general, Atlassian recommends keeping the number of sprints below 60,000. For details, review the Jira Software guardrails for sprints.
If you cannot reduce the number of sprints below the 65,536 total, you can work around this limitation. You can increase the index.max_terms_count OpenSearch setting to support more than 65,536 sprints.
Please note, this will use more resources on your OpenSearch cluster. For more details, please refer to our documentation: Configure index settings on OpenSearch.
Was this helpful?