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

Epic name with umlaut can not display correctly in JIRA issue macro

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 6.13.4, 6.13.5
    • Macros - Jira Macros

      Issue Summary

      The epic name value with Umlaute with the Epic issue cannot be displayed correctly.

      Environment

      • JIRA SoftWare 7.13.3
      • Confluence 6.13.5

      Steps to Reproduce

      1. On JIRA, Create an Epic issue with epic name like "test ä test ö test ü"
      2. Create a Bug issue like to the epic issue above.
      3. On Confluence, Create a new page with a JIRA issue macro filter out the issues above and choose to show the epic name.
      4. Save the page

      Expected Results

      The epic name field should show the normal umlaut characters for all issue type.

      Actual Results

      The umlaut character in the epic name is showing the XML encoded code for the epic issue type.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

        1. Screen Shot 2019-06-05 at 13.07.35.png
          Screen Shot 2019-06-05 at 13.07.35.png
          117 kB

            [CONFSERVER-58379] Epic name with umlaut can not display correctly in JIRA issue macro

            Hannes Medwed added a comment -

            We are impacted as well, but in a slightly different way. We have projects with an "&" in the name and this will be displayed incorrectly as well. This leads to issues and inconsitencies while rendering Charts later on. We also have similar observations to 69b7f8704f00

            Hannes Medwed added a comment - We are impacted as well, but in a slightly different way. We have projects with an "&" in the name and this will be displayed incorrectly as well. This leads to issues and inconsitencies while rendering Charts later on. We also have similar observations to 69b7f8704f00

            Ratheesh E K (Inactive) added a comment -

            https://getsupport.atlassian.com/browse/PSSRV-35710

            Ratheesh E K (Inactive) added a comment - https://getsupport.atlassian.com/browse/PSSRV-35710

            Philippe PEREZ added a comment - - edited

            We are impacted by this issue, and please note that if you do another Jira issue macro this time requesting for all issues inside the Epic and still asking to display the Epic name, then it will be displayed correctly, which is baffling.

            JQL: Key=BLABLA-108 and type = Epic => Epic name wrongly displayed
            JQL: issueFunction in issuesInEpics("Key=BLABLA-108") and "Story Points" is not empty => Epic name correctly displayed

            Philippe PEREZ added a comment - - edited We are impacted by this issue, and please note that if you do another Jira issue macro this time requesting for all issues inside the Epic and still asking to display the Epic name, then it will be displayed correctly, which is baffling. JQL: Key=BLABLA-108 and type = Epic => Epic name wrongly displayed JQL: issueFunction in issuesInEpics("Key=BLABLA-108") and "Story Points" is not empty => Epic name correctly displayed

              Unassigned Unassigned
              yilinmo Yilin (Inactive)
              Affected customers:
              30 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated: