Manage search result limits for Jira Software Data Center boards
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
Jira Software 11.3.12 introduces a search result limit for boards to improve performance. This change aligns board search behaviour with OpenSearch standards by capping results at a default limit.
Diagnosis
Jira Software records disabled state at startup in <jira-home>/log/atlassian-greenhopper.log. Look for this warning:
WARN [web.rapid.list.RapidBoardSearchLimits] Rapid board searches are not
limited because 'com.atlassian.jira.agile.darkfeature.board.search.result.limit'
is disabled. A board whose filter matches a very large number of issues loads a
document per matching issue and can exhaust the heap.If this log message can't be found, then the limit is active. This is the default.
Cause
Starting in version 11.3.12, a new dark feature flag "com.atlassian.jira.agile.darkfeature.board.search.result.limit" is enabled by default. When active, Jira Software applies the value of jira.search.platform.max.result.window (default 10,000) to board issue searches on every search platform, including Lucene. This prevents unbounded search behaviour that can impact system stability.
The limit applies to the backlog, the board in work mode, and the other board issue queries that share the same search path.
Solution
You can either raise the limit or disable it entirely if your environment requires unbounded board searches.
Adjust the search result limit
If you need to increase the number of results displayed on boards without disabling the limit, you can modify the platform search window setting.
Stop Jira.
Edit jira-config.properties in your Jira home directory.
Add or update the property with your desired limit, for example:
jira.search.platform.max.result.window=250004. Start Jira.
In a Data Center cluster, apply the same value on every node.
Restore unbounded search behaviour
If you prefer the previous behaviour where search results were not capped, you can disable the board search limit dark feature flag.
Disabling this flag reinstates the risk of OutOfMemoryError on boards with very large result sets. Prefer raising the result window above, or narrowing the board filter.
Log in as a user with the Jira System Administrators global permission.
Go to the following URL in your browser: <JIRA_BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa
Under Enable dark features, in the Enable dark feature field, enter:
com.atlassian.jira.agile.darkfeature.board.search.result.limit.disabled4. Select Add.
The key now appears in the Site-Wide Dark Features list. To re-enable the limit later, select disable next to that entry.
Was this helpful?