Export limits
The information on this page applies to Rich Filter Results gadgets only. No other rich filter gadget type is subject to any export limits.
To prevent server overload, by default, Jira limits the maximum number of issues exported in one operation to 1000. This limit can be modified by editing the configuration settings or your Jira instance. The properties used to compute the export limits are:
jira.search.views.max.limit
: This property limits the number of issues that can be exported; by default, it is set to 1000. Only certain users can break this limit, see below.jira.search.views.default.max
: This property sets a soft limit (a default value) on the number of issues that can be exported. Any user can decide to break this limit.jira.search.views.max.unlimited.group
: If thejira.search.views.max.limit
property is set, only the users in this group can decide to break the limit.
Rich Filters::PDF Reports for Jira considers these limits before exporting the issues in Rich Filter Results gadgets (see below). These limits do not impact any other rich filter gadget.
1. Exporting single Rich Filter Results gadgets
When you try to export a Rich Filter Results gadget that can potentially break any limit, you are presented with a dialog that allows you to set the maximum number of issues to be exported. You can set the number of issues to be exported (Maximum issues), but you cannot break the hard limit unless you have the rights to do so (see the jira.search.views.max.unlimited.group
property above).
2. Exporting dashboards containing multiple Rich Filter Results gadgets
The same logic applies when exporting the Jira dashboards containing one or several Rich Filter Results gadgets. The difference is that if the dashboards contain multiple Rich Filter Results gadgets, the limit applies to the cumulative total of issues in all Rich Filter Results gadgets together rather than to each gadget taken individually. This mechanism is added to prevent you from circumventing the limits set by the administrators simply by using several Rich Filter Results gadgets on the same dashboard.
Be cautious while exporting too many issues (which also have a lot of columns). It can be resource-intensive for Jira.