Sometimes Pivot Report for Server/Data Center Jira’s fails to export the data to Excel. Cases are very few and typically happen on non-default Jira configurations or wih huge reports of 5,000+ issues.
This issue may be fixed by adjusting POST size, which regulates the maximum size of the file for downloading.
Please be aware that making changes to these files without adequate knowledge and expertise can lead to severe issues, including server failure and data loss. Therefore, we strongly advise that only skilled administrators, who are well-versed in Jira’s configuration and its underlying infrastructure, should undertake such modifications.
To begin with, please check the following article by Atlassian on how to find installation directories and configuration files.
Default value for POST size for Tomcat server (used by Jira) is 2,097,152 bytes (2MB). To increase it, you have to update server.xml
file from Jira configuration. I.e. for default Linux distribution this file can be found in /opt/atlassian/jira/conf
folder. You have to found Connector
section and add maxPostSize
attribute with large enough value (ie 10485760, that means 10MBand should be enought for report with 10k issues)
<Connector port="8080" ... maxPostSize="10485760"/>
See more: Apache Tomcat 8 Configuration Reference.
Also may be necessary to increase POST limit size in reverse proxy server. NGINX server has property client_max_body_size
server {
listen 443 ssl;
client_max_body_size 10M;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_read_timeout 300s;
proxy_pass http://localhost:8080;
}
}
See more: NGINX Module ngx_http_core_module.
If you have any questions or concerns regarding the configuration files or require further assistance, please don’t hesitate to contact our support team. We’re always here to help you navigate through any technical challenges you may encounter.