The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Deprecation of legacy workaround to export >10,000 work items
Hi Atlassian Community!
We’ve previously introduced the ability to export up to 10,000 work items to CSV or Excel. You can learn more about it here.
With this capability, we extended exports, that were previously capped at 1,000 issues to 10,000 issues. With these increased limits, you are able to export larger data sets, and don’t need to piece together data as frequently leading to a smoother experience to create reports on your data.
What’s changing?
As we scale Jira’s exports and modernize our core experiences to be faster for customers, we’re deprecating a legacy exports workaround that allowed users to export more than 10k issues, using URL parameters to incrementally export issues.
This required users to manually merge the results and was limited to exporting 1,000 work items per call. Learn more about the legacy workaround.
How to adjust to the change?
If you previously relied on this workaround, we recommend switching to the expanded in-product export (of 10k) and use JQL filters to narrow your export criteria.
For example, you can use ranges of the 'created' date in JQL to keep each export under the limit while still covering your full dataset over multiple exports.
We’d love your feedback
We want to make sure this works well for you in real-world scenarios. Have you tried the new limit? Are there any challenges we should know about?
Tell us what you think as a comment in this post. Your input helps us shape what’s next.
Was this helpful?
Thanks!
Himanshu Singh
1 comment