Even though there is a work around, we need a better solution. The work around is taking longer time to get the full result and if folks are not that technical in nature, will miss the full execution and wasting their time.

If realtime fetch is taking longer time and causing performance issues, please add a batch mode to get the results , so that system can choose , how to run without impacting the performance.

Completely reasonable and much needed feature request, that lasted 14 whole years just to be about to be considered for implementation.

Bravo, Atlassian. You'd think they'd have won some kind of Guinness world records by now. 

A PowerShell script I wrote

Basically it invokes the REST API for you, pulls issue data and write the result as a CSV file. 
Uses Get-Credential to protect your API token. 
Caveat: I haven't done text formatting for all types of fields. Update the ParseFieldValue function if you want to support the more complex field types. 

To see help message: 
>Get-Help .\GenerateReport.ps1

To use interactive mode: 
>.\GemerateReport.ps1

Thanks, I have used Excel to get Jira data.

Hi 11968eb17a86 ,

You can download in chunks of 1000 records at once using below process.

You can use workaround below.

a) Right-click the URL for export (either "All Fields" or "Current Fields") and select Copy Link Location. The URL should be similar to:

http://localhost:8080/sr/jira.issueviews:searchrequest-excel-current-fields/temp/SearchRequest.xls?query=ER%5C+&summary=true&description=true&tempMax=1000

b). Paste that URL into a different browser tab.

c). Append the &pager/start=1000 at the end of the URL string to instruct JIRA to export from index 1001 and above (1000 rows). And click on Enter

http://localhost:8080/sr/jira.issueviews:searchrequest-excel-current-fields/temp/SearchRequest.xls?query=ER%5C+&summary=true&description=true&tempMax=1000&pager/start=1000

 d. Next export should append the &pager/start=2000 (change from &pager/start=1000 to &pager/start=2000) at the end of the URL string to instruct JIRA to export from index 2001 and above (1000 rows).

e. Repeat the above steps by incrementing Start=$000 based on your ticket volume

like start=1000 (for 1001 to 2000)

, start=2000  (for 2001 to 3000)

, start=3000  (for 3001 to 4000)

so on 

While exporting the Jira issues in CSV format from a Project, its only showing/exporting 1000 records. i can see there are 4000+ records in system. What is the easier solution/option to export all the issues including all fields from Jira?

Please bring back this functionality, it's essential! Thanks!

This is most disappointing. 

Need to get this bug fixed, please.

It's so stupid that we cannot export more than 1000 issues easily.  Resolved it as soon as possible.

Let's go! Why can't this happen in the cloud? 1,000 limit is unacceptable. If Atlassian is worried about network performance or egress AWS charges, figure out how to charge for it. I'd rather give 2-3 staff members governed access to this feature and pay for it selectively than not have it at all. 

This is extremely limiting and needs to be resolved. This ticket was created in 2011!
Manually merging data is extremely time consuming and the column variation of X tickets differs from the first 1000 exported.

Adding on that there really needs to be a better way to pull a list of all tickets in the project so that you can do some basic analytics in external tools like Excel or Power BI. Manually pulling the data 1000 rows at a time a time is not feasible. 

The solution provided is completely incorrect. It is only applicable if the we have select columns and exclude attachments, comments and labels. 

Below scenario is where the Atlassian solution (of consolidating excel exports) does not work and does not cover

When first set of 1000 records are exported, it will be it's own set of multiple columns on Comments, Attachments, Labels - depending up on the number values in each of those 1000 records. For example Row 1 could have 10 comments, 10 attachments and 10 labels. Row 2 could have 15 comments, 15 attachments and 2 labels. Hence export will have 10 attachment columns and 15 comments columns and 10 labels columns

The second set of 1000 rows could have it's own set of columns against comments, attachments and labels etc. 

Manually merging them is a herculean task and humanly excruciating. Hence ,please provide a correct and easier solution.

No amount will ever be enough. Atlassian worries about memory and processor usage while customers worry about not getting all data in one go.

You are better off writing a program/script to call the REST APIs where there are pagination functions. 

Having a limit of 1,000 issues per export creates extra work for us as we have to do multiple downloads and combine them.  Definitely not optimal.  I'm not sure how much of an increase would help.  We need to export issues today in 2 separate fix versions and need it in one report, but one of the fix versions has well over 2,000 issues.  Is is possible to remove the limit on the number of issues that can be exported?

Guys,  This is horrendous.  I have to extract off this years Jira tickets  ... just a limited number of fields including custom items, so I can report weekly on progress to non-Jira users.   But this year for the first time we have more than 1000 tickets, and Jira stalls at 1000.

The instance of Jira is a corporate cloud version, and serves many more teams, that is to say, it is not my teams Jira to muck about with..

Never mind, there is a workaround.  I can export the first 1000, and then export the last few dozen by using   pager/start=1000.

But blow me down, I get a different set of columns for the 1-1000 extract as I get for the 1000+ extract.

WTF??????

I've tried everything.  Varying my number of extracts. I can't get Jira to give me data of the amount or in a reliable format.

Its 8pm in the evening and you've ruined another day.

Hi, we also need to increase the limit. Thanks!

https://getsupport.atlassian.com/browse/JST-899898

Please fix @Vinod, thanks!

Deperately needed, please add this capability!

Hi,

I'm writing on behalf of the entire organisation. We need the limit to be raised so badly!

Je gère plus de 120 projets, j’ai plus de 1700 plans de test, plus de 2200 test d’execution et pour le tout, plus de 11000 test run. Pour extraire tout ça dans excel je dois lancer au total 15 fois mes rapports car bien évidemment pour arriver à tomber en dessous de 1000 lignes pour les filtres utilisés je ne peux que jouer sur les critères de sélection du JQL. J'ai donc 15 filtres donc 15 fois lancer les rapports au total (3 fois les test plan report, 6 fois les test execution report et 6 fois le test run report)
Imaginez le gain de temps si je ne pouvais lancer que une seule fois chaque rapport. 

Could you please prioritize this? This restriction is very frustrating. For me, even the workaround does not work. 

Consolidating batches of 1000 records is not simple when the first batch contains different columns than the second and so on.  I thought this would happen only when you have different projects in the same result set but it does not, it also happens within the same project. Need a better solution, provide at least an option to select columns to export which could limited but that can provide the total number of issues in the result set.

Atlassian may not consider this as a bug as such but it sure is a quality of life feature to allow more than 1000. 
I would've thought you could use pagination on the results and then batch them to the file in batches of 1000 if performance is a concern. I get there might be other browser considerations/limitations but please provide something that makes this process simple. 

When you get scenarios where data needs to be moved from one field to another because you've now merged projects from one server to another and you want to standardize fields so you don't have to maintain hundreds of fields, it really is painful with this 1000 record limit. 

Regards

Is there anything with the dark feature in the cloud to handle this case?

Very frustrating to keep having to split our queries to keep them under 1k. Would love to see this prioritized.

Agreed.  Please provide a viable solution.  Even something that generate multiple downloaded csvs or whatnot.

We did not realise that this excel export limitation exists. We are now finding difficulty in MIS its time consuming. Kindly provide a workaround or fix for the excel/CSV max number of records export. 

Hi there, i'm facing the same issue as the users above.

Use Case

• We run mass lab tests that may number above 1,000 at the time and need the input CSV to accept up to 10,000 rows
• We run similar reports where we need to export the same (up to 10,000) lab tests onto a local db/excel

Due to the current limitations, some of my teams cannot use Jira as the workflow processor and are reverting back to using excel.  you can imagine the email traffic this generates.

Please consider increasing the limit or a work around in future releases.

When running an advanced search it is also very frustrating that the count of returned issues is limited by the '1 of 1000+' description. I want to know how many issues have the searched condition, not that there are more than 1000.

We recently migrated to the cloud, and did not realize that this limitation exist. This is impacting monthly process, and would be very please to see Atlassian picks this up, and making the export issue number bigger.  

moreover, when i ask for the report test run, i can import more than 3000 lines, i still don't understand for for example test list report i have to multiply my filters in order to only have less than 1000 lines in my report.

A limit of 1,000 issues is simply too small for a lot of the work that is required for me and my peers. The workaround is extremely tedious and time consuming. I think a limit of 10,000 makes more sense. Please fix this!

I am a huge fan of the Atlassian products but sometimes amazed by some of the limitations of the Cloud product. I do understand the need to throttle the potential for performance hits from Cloud sites smashing their DBs with large queries but there must be a better work around for this issue. 

It's a bit silly that I can't export more than 1000 rows. I understand saving server processing but there is no alternative to getting all the data in one go. 

Please fix ASAP.  I think increasing it to 10000 - 20000 would be acceptable. Currently, we are having issues trying to complete the Post Production work for Jira Migration where there are so many duplicated fields created as a result of the JCMA tool. We have over 120K issues that need to be copied and cleaned up. It will take forever babysitting to do the export and import of the issues which we calculated will take over 10 days continuously for 24 hours. Currently, it is not a viable solution with a limit of 1000.

At least temporarily to increase on a need base that we can request through support.

c'est d'autant plus handicapant quand on génère un rapport de +1000 lignes et que l'export vers excel ne prend que les 1000 premières lignes sans signaler que ce n'est pas l'intégralité du rapport qui est récupéré.

The work around in https://confluence.atlassian.com/jirakb/increase-issue-limit-for-excel-exports-in-jira-cloud-779160811.html is not sustainable. That is a flimsy response. When will this setting be available in Jira Cloud so that it can be modified. I have yet to find a rationale why this is not currently possible 

Please fix!

This issue needs to be fixed immediately. It is INSANE that this is still a problem. 

Hi @Nagendra M,

That's not a plug-in for Excel, that's Google Sheets - it's not the same thing by a country mile.

They did anounce an Excel plugin, but it won't install for 50%+ (at least based on the comments) of the people (myself included) who want this because we want REAL Excel support, not some contrived hack.

Hi All,

Jira provided new Free Plug-in to export Jira issues into Excel it's very fast and easy.. I hope the help.

URLs: https://gsuite.google.com/marketplace/app/jira_cloud_for_sheets/1065669263016

https://gsuite.google.com/marketplace/app/jira_cloud_for_sheets/1065669263016

Thanks. 

100% agree and the product seems like its going nowhere, the same issues have been sitting around for years.

Why is it every time I try to do something in Jira Software I hit a brick wall.   How many story points are building up on my backlog... sorry we don't do SUM operations in search or reports but you can export to Excel and do it yourself.  Ok.. After an hour of trying to figure out why my reports were slightly off I discover the 1000 rows in excel which led me here. So now I have to build my own query, export the first 1000 to excel, then use a URL workaround to export the rest, the merge the datasets, build the summation and groupings and report on the data.  Every Monday Morning.  And we know what is coming next.  A comment that for 10.00 a month you can buy a plugin that summarize, then 10.00 a month for grouping, then 10.00 a month for the next thing.  Jira is not useful for anything more then a couple programmers.   

Closed with a resolution of "Won't Do" do you even care about the users?  If we did this in a production system we would be totally slammed by our users.  And the fact that nothing tells you this - that it is a silent bug you only find out about by obscure means.  Once again another reason I regret we had to move to Jira - we did so only because of global company policy - not because it was in any way a better platform.

Resolved - Are you kidding me !! A system that cannot export the issues for reporting which is required as Jira reporting is so poor.

Do these people ever do anything about any of these requests? All I see are a bunch of much needed functionality that people have been requesting for years and nothing ever gets done.

Why did we choose this system????

+1 for addressing this.

The ability to export more than 1,000 rows, without a time-consuming workaround, is a basic feature that I'd expect any enterprise application to support. As others have pointed out, the current UI is also extremely confusing and give the user no notice that the exported data is limited.

At a minimum couldn't you at least put some text in somewhere that lets the user know this limit is in effect?  

It's frustrating that this limit isn't changeable; it's also frustrating that there's no way to know this is happening.  

In practically all web apps, the convention is that, sure, on-screen results are paginated, but export/download gives the whole lot.  

Super disappointing, Atlassian.  Then again, it is in keeping with the Jira style of random obfuscation.  :| 

I would like to echo the concern by @jesse Young, this is much needed feature and very time consuming to export by workaround.

It's hard to believe this has not been supported yet. It's a pain to export and provide detailed reports without this. Instead I'm forced to use a workaround...

Ryan is right - this is a broken feature. The user shouldn't have to go to Google to find this BS built-in limitation. Very disappointing. 

Agree with the above - please fix this!

This is literally a broken feature. The UI doesn't even inform the user that the export is limited to 1000 issues.

Jira, get with the program and fix your software. To be honest, it is things like this that make me want to stop considering Jira as a solution. It strikes as intentionally making the software useless so that you can push your marketplace.

How do you expect to deal with big enterprises?

Kerrod, this resonates with plenty of users. Atlassian's continued middle finger to its customers and to UX practices is why your customers are leaving. Bye. PS your software is shitty.

Jira is becoming more and more useless. I can't get the info I need from filters, and I can't export the data to SQL server for queries. Time to find another product.