Epic Link in Jira Issue Macro that connects to Jira Cloud not showing Lozenge Color and Hyperlink when Epic Summary includes single quote

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 7.16.4, 8.5.1
    • Component/s: Macros - Jira Macros
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      Epic Link in Jira Issue Macro that connects to Jira Cloud not showing Lozenge Color and Hyperlink when Epic Summary includes single quote.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Install Confluence Server/DC and configure Application Link with Jira Cloud
      2. In Jira Cloud:
        • Create Epic that include single quote as part of the Epic Summary
        • Create story that link to the Epic above
      3. In Confluence Server/DC:
        • Insert a Jira Issue Macro that shows the story created above
        • Make sure Epic Link field is configured to show in the macro
      4. View the Confluence Page with Jira Issue Macro

      Expected Results

      Epic Link should:

      • show as Epic Name
      • have the correct colored lozenge
      • have the correct hyperlink to it's Epic

      Actual Results


      Epic Link is:

      • show as Epic Summary
      • not showing as lozenge
      • not having any hyperlink

      In Confluence, the error message can be seen becuase the single quote wasn't escaped as part of the JQL:

      2023-09-12 06:11:59,006 DEBUG [http-nio-8090-exec-12 url: /rest/jiraanywhere/1.0/jira/renderTable; user: admin] [org.apache.http.wire] wire http-outgoing-932 << \"{\"errorMessages\":[\"Error in the JQL Query: Expecting ',' or ')' but got 's'. (line 1, character 69)\"],\"errors\":{}}[\\r][\\n]\"
      

      This can also impact other Epic Links in the same Jira Issue Macro despite they don't include single quote in the Epic Summary, because the JQL failed as a whole.

      JQL that was sent
      issuetype = EPIC AND 'Epic Name' in ('Same Epic Name/Summary','What's New')&fields=customfield_10011&fields=customfield_10012&fields=customfield_10013&fields=summary
      

      Information

      The same issue does not happen when Confluence Server/DC is retrieving same set of data from Jira Server/DC.
      This is because the XML Response from Jira Cloud did not provide the unique Issue Key for Epic Link, but Epic Summary instead.

      While this has the same outcome as CONFSERVER-91467, but the cause are different

      Workaround

      In Jira Cloud, avoid using single quote as part of the Epic Summary

            Assignee:
            Unassigned
            Reporter:
            Damien Tan
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: