Excel and Word Export Retuns Zero Results Due to International Characters
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Any Word or Excel export which is done when using a filter which a search text of an string with umlauts will return zero results.
Cause
The cause of the problem was that the parameter useBodyEncodingForURI="true" is not set. This causes umlaut characters to be lost when the export is made. Example:
1
2
3
4
<Connector port="8080"
maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" useBodyEncodingForURI="true"
enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"
/>Resolution
Add useBodyEncodingForURI="true" to server.xml and restart JIRA.
Was this helpful?