We were previously using Jira v7.3.2 server and users had the ability to export more than 1000 issues at a time. It appears that there was a bug allowing users to bypass the Jira's default limit exporting of up to 1000 issues.
We're now using 7.6.9 which appears to have plugged that gap and prevents users from going over that limit by presenting an error.
I know the answer is very much depedant on spec of machine and userbase but has anyone changed the export limit and to what? Or is the recommendation to leave it at 1000 regardless of base size / number of users using the instance.
It is a bit more complex. Off the shelf, there's a 1,000 limit, but you can override it with a parameter in the url. As lots of people then break things by using that parameter, there's a setting admins can set that locks it down, banning the parameter as well (or rather, restricting it to certain accounts).
It's likely your 7.3 server allowed people to go over 1,000, but I seem to remember the hard block was implemented by default in a later version (because of so many admins complaining about people taking their systems out with the override)
I've managed to get 100,000 out of a system once, but that was with no other users and a stupid amount of resource thrown at it. The 1,000 limit was a good limit for older computers, but I still wouldn't recommend increasing it for most people.
I will always ask why people are exporting that much - 99% of the time, it's for reporting that they then mangle to misrepresent the data. It would be better to invest in proper reporting tools.
I do not remember any bug. It was possible to change the limit and make exceptions to specific groups. All info about this you can find in below documentation
You can also read that Atlassian made a improvement to search and new versions of Jira (including new Enterprise version) have this implemented. So when switching to this version is is OK to increase the default limit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.