JIRA allows you to view search results in several different formats, including Word, Excel, RSS or XML.
A search view that returns too many issues can take a long time for JIRA to complete and can use a large amount of memory. It can be a factor in OutOfMemoryErrors in JIRA.
An large RSS feed of search results can be particularly problematic, because:
- the user's RSS reader will continue to make the request periodically (for example, every hour)
- since the RSS reader makes the request, not the user directly, the user is unaware that the request takes a long time or is failing
You can use the following three properties in jira-application.properties to limit the number of issues returned by a search view.
See Making changes to jira.application.properties for the details of how to make and apply changes to jira-application.properties.
jira.search.views.default.max sets a "soft" limit on the number of issues returned. It has a default value of 1000. You can set it to, for example, 100 as follows:
For an RSS or XML view, JIRA applies the limit by appending the
tempMax parameter to the URL of the search view. For example:
In the above example, JIRA will limit the number of issues returned to 200 (in this example).
However users can override this "soft" default by removing the
tempMax parameter from the URL or by increasing the value of
jira.search.views.max.limit sets a "hard" limit on the number of issues returned. It is disabled (commented out) by default. You can set it to, for example, 200 as follows:
If a user makes a issue view request that would return more than 200 issues (in this example), JIRA does not return the issues but instead returns a 403 (Forbidden) error. While the user might not be happy, it prevents JIRA from consuming lots of resources and possibly running out of memory.
Make sure you set the value of
jira.search.views.max.limit to greater than or equal to the "soft" limit set by
jira.search.views.default.max. Otherwise all search views that would return issues limited by the default "soft" limit will instead return a 403 (Forbidden) error.
You may have a requirement for most users to have the limit imposed on them, but a few users to be exempt from the limit. One example of this is if your JIRA instance is Internet facing. You may want external (Internet) users to have the limit imposed on them, but for internal users to be able to produce unlimited search views. You can use the
jira.search.views.max.unlimited.group parameter to achieve this.
jira.search.views.max.unlimited.group property is disabled (commented out) by default. If you enable it, you must set it to a valid group or leave it empty. For example: