Accented characters not displaying correctly in Jira server

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

Summary

Symptoms

  • The special characters as in French or German are not display and parse to Database correctly. For example, during the issue creation or other request via REST API.

  • Some gadget name that has the special character also not displayed correctly. For example, "Filtres préféré" is shown as "Filteres pr?f?r?"

Diagnosis

  1. Right click on the action that you want to perform then open the dialog box in a new table and perform the action to check whether the character encoding is correct.

  2. Double check whether the setting "webwork.i18n.encoding" in the system information had been correctly set to UTF-8.

Cause

The webwork action is actually using the encoding setting of "webwork.i18n.encoding" rather than the setting 'URIEncoding=UTF-8' and '-Dfile.encoding=UTF-8' in the JVM parameters, and it will be overwritten by the same setting in the following place:

  1. $JIRA_INSTALL/atlassian-jira/WEB-INF/classes/webwork.properties

  2. jira-application.properties

  3. In the database:

    1 select * from propertystring where id in (select id from propertyentry where property_key='webwork.i18n.encoding');

Solution

Resolution

  1. Correct or Remove the extra configuration in the properties files.

  2. Update the settings in the database.

    1 update propertystring set propertyvalue = 'UTF-8' where id in (select id from propertyentry where property_key='webwork.i18n.encoding');
Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.