Cannot search issues that contain umlaut characters in link
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
Umlaut contained in link with JQL component search not properly encoded
Steps to reproduce
- Disable new project navigation
- Open the Project summary page
- Click "Issues"
- Click on a component containing an umlaut in the section "Unresolved: By Component"
- The issues with that component are not found but an error message like Capture.PNG is displayed
Cause
Reverse Proxy
Workaround
- The issue is only reproduced when accessing JIRA using reverse proxy. By-passing is a temporary workaround.
- Stop JIRA.
Add an extra http connector to server.xml :
<Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8081" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true"/>
- Start JIRA
- Access JIRA using IP:port, for example http://10.1.1.123:8081
- Verify if the issue still occurs.
- If the issue still occurs, please raise a support ticket to Atlassian Support