JIRA has set that limit because this operation is so resource extensive (it puts too much load in your system). Before I suggest the workaround, may I first suggest that you do the export in batches? Update your JQL to trim down to 1000 issues or less and repeat it as needed so it will not affect your JIRA.
Hi Gabrielle, Please could you tell the work around as configuring the batches won’t be efficient for us and also runs the risk of missing an issue (part of this exercise is to track miss/un categorised issues) We are not worried about the load on our system in this case. Thanks Alistair
Go to your System Administration > Troubleshooting and Support > System Info. Search for the "jira.search.views.max.unlimited.group" key and get the group name. Accounts added to this group will have godly powers on exporting/viewing issues (unlimited). If you can't see this, try configuring it in the server side (https://confluence.atlassian.com/display/JIRAKB/Exporting+a+filter+result+containing+more+than+1000+issues).
Bear in mind that the higher you go over 1000, the more likely you are to cripple your system and lose the export to a timeout or resource overload anyway. If you really want several thousand or more, then you *really* need to heed what Gabrielle says and batch it up. Or, better, examine the reasons you're doing this and come up with a better approach to solving the problem. Why are you trying to do massive exports like this?
Hi Nic, Sorry for the delay getting back to this issue raised (have been out for a while), I've also been following up with Tempo. I'm reporting on time logged but Tempo doesn't offer the "Epic Name" associated with the Issue ID. So I am trying to export this now using the issue API and link the outputs together. The problem is that I still cannot raise the amount of data returned above 1000 (can't seem to find the setting described above). Also I cannot restrict the XML date range easily. Note: I am on the cloud system. Any help would be appreciated. Thanks Alistair
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs