Apache output to excel limited to 1000 rows

Peter Trubshaw
Contributor
November 27, 2011

Hey there,

This is an old problem, but recently reared its head again in 4.4.3. I have followed the instructions on http://confluence.atlassian.com/display/JIRAKB/Export+More+Than+1000+Results+to+Excel to no avail. This article mentions - *note that the server may forbid this, see below* but there is nothing below that it refers to?

I have updated/jira-config.properties; with the jira.search.views.default.max = 1500 - but I get an Apache error _You are not allowed to get a result set of more than 1000 results. Current search returns 1068 results_

in the past we have modified the tempmax param on the URL

5 answers

1 accepted

2 votes
Answer accepted
Dalectric
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.
November 27, 2011

Fixed it; you need to add the following

jira.search.views.max.limit=-1

to

jira-config.properties

1 vote
Nic Brough -Adaptavist-
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.
November 27, 2011

I think you've misunderstood. Setting the jira.search.views.default.max = 1000 creates an absolute cap which users cannot override by changing the default "tempmax=1000" to "tempmax=<larger number>" - when your search for 1068 runs, it is now running into that 1000 limit and doing exactly the right thing - telling you that you're over the limit (that is the "server may forbid this" thing that you are being referred to)

To get more than 1000 rows, you should comment out that line so that there is no cap (OR, use the "this group is not limited" line below it in the file) and override tempmax in the url.

Peter Trubshaw
Contributor
December 12, 2011

I understand it, but the link leads people (ok, me) to the wrong conclusion - that is you can update this setting to get increase the number of rows returned (to more than 1000), but that is not true.

To increase it to more than 1000 you need to set the jira.search.view.max.limit to either -1 or a value above 1000.

0 votes
Peter Trubshaw
Contributor
December 12, 2011

To increase it to more than 1000 you need to set the jira.search.view.max.limit to either -1 or a value above 1000.

0 votes
Sultan Maiyaki
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.
December 4, 2011

Please note that if you are getting a 403 forbidden error, it is due to the fact that the value specified for jira.search.views.max.limit is lower than jira.search.views.default.max. Therefore I will suggest you raise jira.search.views.max.limit to a higher value or -1 to make it unlimited.

0 votes
Dalectric
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.
November 27, 2011

There is an issue here (JIRA 4.4.3). I've set the line in

<jira-home>/jira-config.properties;

as

jira.search.views.default.max = -1

and get the Apache error. (I have also used 0). I will have a look around to see if I can find a resolution.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events