Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-54583

Jira Issue Filter doesn't work when unicode characters are used.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 6.4.2, 6.13.4, 7.13.5, 7.13.7, 8.5.19
    • Macros - Jira Macros

      Summary

      If you insert an unicode character in the Jira issue filter, Confluence will fail to retrieve the issues from Jira. This happens after publishing the page, but it doesn't happen when you preview the page.

      Steps to Reproduce

      1. Go to Jira and create a new project called "Não"
      2. Go to Confluence and insert a JIM with the following filter: 
        project = Não
      1. Preview the page.
      2. Publish the page.

      Expected Results

      Confluence will display all issues from the project "Não" as it happens on preview.

      Actual Results

      The following message will appear:

      Refresh didn't work. Try again or click an issue to see it in Jira.

      Notes

      Workaround

      1. You can save the JQL query as a filter and then use the JQL "filter = <filter ID>" in the JIRA issue macro.
      2. Adding the following to the JVM startup options could fix the issue as well: 
        -Dfile.encoding=UTF8

        1. screenshot.png
          screenshot.png
          53 kB

            [CONFSERVER-54583] Jira Issue Filter doesn't work when unicode characters are used.

            Theodoros Antoniadis added a comment -

            I have the exact same problem even when I use the filter ID ("Filter = 99999")
             
             

             

            Theodoros Antoniadis added a comment - I have the exact same problem even when I use the filter ID ("Filter = 99999")      

            Junio Fernandes added a comment -

            I found a solution:

            https://confluence.atlassian.com/confkb/filesystem-encoding-is-written-as-ansi_x3-4-1968-even-though-the-server-is-set-to-utf-8-658735809.html

            In System Information, my Confluence was configured with Filesystem encoding ANSI_X3.4-1968. After applied the KB, problem was gone.

            Junio Fernandes added a comment - I found a solution: https://confluence.atlassian.com/confkb/filesystem-encoding-is-written-as-ansi_x3-4-1968-even-though-the-server-is-set-to-utf-8-658735809.html In System Information, my Confluence was configured with Filesystem encoding ANSI_X3.4-1968. After applied the KB, problem was gone.

            Junio Fernandes added a comment -

            Changing "ã" by "\u00E3" works. But it's not the solution. It should accept special chars as in Jira search.

            Junio Fernandes added a comment - Changing "ã" by "\u00E3" works. But it's not the solution. It should accept special chars as in Jira search.

            Artem Chatlikov added a comment -

            I wouldn't say this should be low prio. We have encountered this same issue.

            Only workarounds are removing elements causing problems.

            In our case it was labels -> create same labels without special characters (so for example change ä -> a ö -> o) and bulk change all issues with that old, problematic label to new, corrected label.

            Much harder to work around for example project name, that was mentioned in this issue.

            We have this issue in Confluence 6.3.2 so that should be added to Affects Version/s.

            Artem Chatlikov added a comment - I wouldn't say this should be low prio. We have encountered this same issue. Only workarounds are removing elements causing problems. In our case it was labels -> create same labels without special characters (so for example change ä -> a ö -> o) and bulk change all issues with that old, problematic label to new, corrected label. Much harder to work around for example project name, that was mentioned in this issue. We have this issue in Confluence 6.3.2 so that should be added to Affects Version/s.

              Unassigned Unassigned
              gviana Guilherme V. (Inactive)
              Affected customers:
              30 This affects my team
              Watchers:
              29 Start watching this issue

                Created:
                Updated: