Recently this was fixed to have exports recognize a limit:

• https://jira.atlassian.com/browse/JRASERVER-63239

The problem is that if users simply do a search that returns more than the max limit, they'll hit an error with no details on how to workaround the problem.

In the past, before JIRA 7, the exports would by default set tempMax to be 1000. But with the new exports, the default does not have a limit, so users will commonly run into the forbidden error.

With that, issue exports should do the following:

1. Automatically have the tempMax parameter set as default to match the max limit
2. Provide instructions on how to change the tempMax limit.

Example of error:

Workaround

1. Append the URL with &tempMax=1000

 Check an example script at https://confluence.atlassian.com/jirakb/exporting-jira-s-issues-using-csv-in-batches-1071829731.html