A fix for this issue is available to Server and Data Center customers in Confluence 7.3.2
Upgrade now or check out the Release Notes to see what other issues are resolved.

Hey Philipp,

thank you for your answer. It works now.

Hoping, Atlassian will fix it soon

Regards,

Adrian

Hi Adrian,

although the .bat is indeed the correct file under Windows, it will completely be bypassed when you run Confluence as a Service.
Hence, as you already assumed, you will need to add the parameter in the JVM-Settings of the service.
Btw, it makes sense to add this for Jira too if you haven't already, as otherwise special characters in Confluence page names will be broken when displayed in Jira issues (i.e. when an issue is mentioned on a specific Confluence page).

Regards,
Philipp

Hey there,

I've managed to modify following files

1. bin/setenv.sh  

   CATALINA_OPTS="-Dfile.encoding=UTF-8 ${CATALINA_OPTS}"

1. bin/setenv.bat

   set CATALINA_OPTS=-Dfile.encoding=UTF-8 %CATALINA_OPTS%

We are running on Windows Server (reason for editing bin/setenv.bat) and Jira is running as a service.

The problem is still occuring: 

http://domain/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ITSD+AND+type+%3D+%22Neuanforderung%2F%C3%83%E2%80%9Enderung%22+AND+resolution+%3D+Unresolved+ORDER+BY+%22Punkte+Priorit%C3%83%C2%A4t%22+DESC%2C+status+DESC++&src=confmacro

Do I need to modify the Service-JVM-Settings?

Best regards

Adrian

Hi yourforest,

Thanks for using Atlassian products and I'm sorry that you're affected by the problem.

If your problem is actually caused by this bug, you should be able to solve it with the workaround written in the description.

1. Stop Confluence
2. Add the following line into the bin/setenv.sh file

   CATALINA_OPTS="-Dfile.encoding=UTF-8 ${CATALINA_OPTS}"
   

3. Start Confluence

Could you give it a shot please?

Cheers,
Yuki

Hi ,We also met problem on Confluence 6.11.2 to Jira 7.12.1 

Chinese charters cant be used in Jira issue Filter. 

Is this a bug?

Hello Mr. Tapper,

nice to read you again.
We never had this issue running on Jira 7.1.x and Confluence 5.9.x either.

Since this issue started with our upgrade, we used the start up parameter described in the workaround section and it works like a charm.

Using this parameter in Jira also fixes the issue there, that Umlauts in Confluence page names aren't properly displayed in "mentioned in"-hyperlinks within Jira issues.

Regards,
Philipp Sendek

Entering jira issues macro in markup works for me

e. g.

{jiraissues:url=https://jira.atlassian.com/issues/?jql=text%20~%20%22%C3%A4%22}

the confluence wiki markup editor (ctrl-shift-D) is useful for complex queries, see field description: https://confluence.atlassian.com/doc/jira-issues-macro-139380.html

renderMode=dynamic may be required for multiple queries on the same page and seems to works only for Jira users whose language is set to English

We can confirm this bug in Confluence 6.9.3 and Jira 7.10.2 with the following JQL-query.

issuetype = Frist AND status in ("Frist akut", "Frist überfällig") AND (Verantwortlicher = currentUser() OR Vertreter = currentUser()) ORDER BY Verantwortlicher ASC, due ASC 

So for us, it's basically "just" Umlauts.

Another workaround was to use 'Filter = "Filter_Name_or_ID"' in the JQL, but that obviously requires more settings to be made within Jira itself.

Regards,
Philipp Sendek

Hi Atalssian

We in the Danish Ministry of Education - also have the mistake - and will encourage it to be corrected.

Sincerely

Morten Bjerregaard