Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

You Asked, We Delivered: Export Up to 10,000 items from Jira 🎉

Hi,

I’m Tanya, a Product Manager on Jira Cloud, and I’m excited to share an update you’ve been asking for! We know how important it is to get your data out of Jira when you need it—whether it's for reporting, analysis, or sharing with stakeholders. That’s why we’re excited to announce that you can now export up to 10,000 issues to CSV or Excel from the issue navigator.

Previously, exports were capped at 1,000 issues, which we heard was limiting for many of you. As of March 19, 2025 Sydney/Melbourne time, we’ve increased the limit to 10,000 issues. This means bigger data sets, less slicing and dicing, and a smoother experience all around.

➡️ For customers who still need to export more than 10,000 issues, we’ve updated our support article with a new workaround that helps you get what you need. Read how to export more than 10,000 issues.

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? Did it improve your workflow? 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.

 

Thanks for helping us make Jira even better,

The Jira Cloud Team

7 comments

David Nickell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2025

I remember as a Project Manager back "in the day", how the 1,000 item limit would occasionally impact the way we had to pull issues out for excel and other purposes.   Once I figured out how to paginate with the API's, I was able to work without any problems.

I mention this in the event any other API users built reporting or other features with a hardcoded "1,000" max in mind.  Hopefully your pagination code is dynamic and whether 100 or 1,000 or 10,000 - your code reacts the values being passed in the REST Response.

I also hope this doesn't blow up any systems that can now experience 10x the data volume from a REST call than it used to.  

Well - I don't mean to be "David Downer" on this one -- I think it is great.  Just keep an eye out for sudden data anomalies.  

 

Like • Matt Doar _Adaptavist_ likes this
Tanya Maddalena
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 23, 2025

Hi @David Nickell 

Just to clarify—this export limit increase applies specifically to the CSV/Excel export from the issue navigator UI and does not impact the REST API. Pagination and limits for API-based exports remain unchanged, so any existing integrations or scripts using the 1,000-item limit should continue to work as expected.

Also, a quick reminder (as noted in Workaround 2 of the support article): it's crucial that you do not combine exports from the UI with batch exports using the API workaround. Mixing these methods can result in duplicate or missing work items in your export results. If you're using the workaround, make sure to conduct all exports using that method exclusively, and remember that each batch has a maximum of 1,000 work items.

We really appreciate your insights and support—thanks again for helping us make Jira better! 🙏

Like • 3 people like this
David Nickell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2025

Thanks and I have (for my education) witnessed the limit still at 1,000 in the API. If you think my comment might confuse someone, I (or I assume you) can delete it .   Thanks for the info.

Yatish Madhav
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 24, 2025

Thanks @Tanya Maddalena - this would have helped me a few years back! :D

But I truly appreciate this update! I am very certain it will help me and others in future too! Especially since so many users still find great comfort in working in Excel/CSVs (spot the subtle frustration there hehe)!

Like • David Nickell likes this
Fred Quintero March 25, 2025

Hey team!

How do we know if this is live or working in our instance? I am performing a test export pull with a little over 1000 tickets and I am still limited. The export automatically downloads and there is no loading so I never get the export loading showed in this article: https://confluence.atlassian.com/jirakb/export-over-1000-results-in-jira-cloud-779160833.html

Thanks!

 

Like • David Nickell likes this
David Nickell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 25, 2025 edited

Altering my earlier comment ... in this instance, work item is the same as an issue.  Per my friend ChatGPT ..

"Using the asynchronous Export CSV feature”

  • This refers to a newer, more scalable CSV export method that processes in the background.

  • With this method, you can now export up to 10,000 issues (a.k.a. work items) in Jira Cloud—so long as you're using this async CSV export, not the regular export buttons.

 

Net of what I am reading -- double check to be sure you are executing the Asynchronous Version.  When I did a test, it seem Async (with the progress bar as mentioned) was the default

 

Lianne Geerlings
Contributor
March 27, 2025

Great improvement for exporting bigger projects.

You can do it all at once instead of creating multiple exports! 🙌🏻

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events