Jira: Export to Excel function only export 1000 rows

[Anthony Kong]

I am trying to export all the jira into a excel spreadsheet. I realised it can only export 1000 rows even if there are more than 1000 in the issue navigator. Is there a work around?

I can apply a filter on creation date to limit the size of the result set. But is there a better solution?

[jhammons · Accepted solution]

Tony,

Please refer to the following KnowledgeBase article:

* http://confluence.atlassian.com/display/JIRAKB/Export+More+Than+1000+Results+to+Excel

Please let me know if I can be of further assistance.

Be well,

Jason Hammons

Atlassian - San Francisco

[Anthony Kong]

All good now! thanks

[Deleted user]

Jason,

This was helpful, but this is a change at the file level. Is it possible to get this fixed for JIRA STUDIO users as well?

[Nic Brough -Adaptavist-]

1000 is a number judged low enough to avoid the performance problems a large export causes. If you need it changed, you'll need to talk to your Studio provider. They're unlikely to increase it because of those problems.

A far better question might be to ask why you're exporting 1000s of issues - Most of the time, it usually means someone doesn't know how to use Jira and a little training will get them working far more efficiently than messing around with spreadsheets (that are obsolete as soon as they're downloaded). In some cases where it's valid, you'll find there are better ways of getting there as well.

[Deleted user]

Nic,

I agree that I might not be as expert in JIRA as you are and would welcome any training coming my way which can make me an "expert".

We are using JIRA Studio (provided by Atlassian themselves) and they have restrictions on developing our own styles of reports. They have restrictions about using other plug-ins as well. So, the easiest way for us was to fall back on Excel sheets to get the reports. I agree that the report might not be dynamic (and can be obsolete as soon as it is created), but it is proving helpful to us.

The data that I've been exporting to the report has been less than 1000 till date except for once and that was when I realized about this limit.

The question was just a normal enquiry and we can actually live with this limitation for the time being.

[Jerome Kern]

Hello @Nic Brough - I will give you an example of why it is needed to provide more than 1000 lines returned. 

Companies that are publicly traded are required to follow and maintain SOC guidelines.  We are audited annually to ensure these guidelines are followed.  Auditors require us to provide them a list of customer opened tickets.   Since we have more than 17000 tickets a year it is pertinent that Jira allow us to provide this information.  In addition to the results we need to provide screenshots of the query used to derive the said results.  I see that this issue has been ongoing now for well over 8 years.  When is Atlassian going to provide a solution to it?

[Levente Szabo _Midori_]

Yes, this is a very real requirement. Atlassian is unlikely to go down this path due to the high risk of degraded performance at a sizable segment of their customers. Clearer communication or more accessible documentation would be welcome, but folks usually are able to solve this by following instructions found in community posts like this.

By the way, I recently posted a somewhat similar use case story where the team (finance industry) needed to comply with SOC1, by exporting the complete records of all their customer transactions to PDF format out of Jira. That wasn't a small feat, either.

[TothJ]

the url of excel export looks like this: http://xxxxx.xxx.xx/sr/jira.issueviews:searchrequest-excel-all-fields/temp/SearchRequest.xls?&pid=10170&status=5&sorter/field=issuekey&sorter/order=DESC&tempMax=1000

tempMax=1000 is the parameter you have to change. you wana change it at one query or wana make it permanent?

[Anthony Kong]

One query is OK. But still interested to know how to make it permanent

[Swapneel Mohite]

Changing the 1000 to more than 1000 doesn't help

[Nic Brough -Adaptavist-]

This thread is four years old. But still valid - changing tempmax won't help if your JIRA has been locked to prevent you overloading it by increasing tempmax.

[Swapneel Mohite]

Thank you Nic for a quick reply.

[Andrew Boeger]

So I just went through this and was really annoyed by the filter - but then I just linked my sheet to Jira with the Jira excel plugin and found you can get any number of tickets into your sheet all at once if you do that. You just have to use the Excel button at the top of the screen instead of exporting to a CSV. 

[Fara Saeedi [Administrator]]

The excel export can get more than a 1000 which is great, however does not provide the capability of exporting all fields the same way export to csv (all fields) can extract all fields (instead of the ones that can be displayed). This is great for some use cases but would not work for other ones.

[Nizam Ahmed]

I collect a filter that produces 2500+ rows of records.

I split them by appending the following to my csv url:

1-1000:

?jqlQuery=&tempMax=1000&pager/start=1

1001-2000

?jqlQuery=&tempMax=1000&pager/start=1001

2000-onward

?jqlQuery=&tempMax=1000&pager/start=2001

It works.

Then I append them in Excel.

[Olivier GALLAS]

Yes but you can't export with some custom columns....

[Moresimp]

Hi there,

With ImpEx, you can export more than 1000 issues.

You can find it on the Atlassian Marketplace:
https://marketplace.atlassian.com/apps/1215792/impex-import-export-from-to-ms-excel?hosting=server&tab=overview

(And it is also available for Data Center!) :)

Best regards, Mark

[Raul Pelaez]

Wait my plugin in few days in the MArketplace and FREE

https://jirasupport.wordpress.com/2016/04/12/new-plugin-is-coming-enlarge-your-excel-export/

[Job]

Found it: there's also a jpm.xml with the values of jira.search.views.default.max and after updating the values there to 2000 the default is now set to 2000 and exporting goes well.
Found it in this link: https://confluence.atlassian.com/display/JIRAKB/Export+More+Than+1000+Results+to+Excel

[Job]

This may be an old post; however we see this limit is still in place. (running on JIRA 6.0.7 at the moment)

I have tried to update the jira-config.properties and added these rows:

jira.search.views.default.max = 2000

jira.search.views.max.limit = 2000

This seems to have no effect because the limit at exporting is still 1000 rows (even after restarting JIRA and rebooting the server and emtying the browser cache  )

After updating the jira.config.properties the export button also still has the &tempMax=1000 at the end. Changing the url to &tempMax=2000 returns a 403 error (forbidden)...

Anything else i can try to lift the limit up to 2000 rows...?

Kind regards,

Job

[Job]

Also added this one to the jira-config.properties: jira.search.views.max.unlimited.group = jira-administrators but it dit not have an effect. (and the user i am exporting with is part of the jira-administrators group)