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

JIRA Issue Macro Icon Does Not Render According to Display URL

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Steps to Reproduce

      1. Setup Confluence with URL: http://localhost:10570/confluence/
      2. Setup JIRA with URL: http://localhost:7315/jira/
      3. Setup Application Link between Confluence and Jira.
      4. Update Confluence with URL: http://localhost:8090/confluence/
      5. Update JIRA with URL: http://localhost:8091/jira/
      6. Update Display URL to http://localhost:8091/jira/ in the Confluence Application Link configuration.
      7. Create a JIRA Issue macro.
      8. Observe the links using browser developer tools.

      Expected Behaviour

      JIRA issue macro should be rendered according to Display URL.

      Actual Behaviour

      JIRA issue macro icon is rendered based on Application URL.

      Note

      The icon might not be rendered if Display URL is updated with Jira URL link that contains SSL (https) or proxy integration (redirection).

        1. config.png
          config.png
          121 kB
        2. JIRA Report Blueprint - Change log.png
          JIRA Report Blueprint - Change log.png
          95 kB
        3. screenshot-1.png
          screenshot-1.png
          4 kB
        4. tes1.png
          tes1.png
          495 kB
        5. test2.png
          test2.png
          481 kB

            [CONFSERVER-36648] JIRA Issue Macro Icon Does Not Render According to Display URL

            That is Great, Many thanks!

            Jean-Claude Passy added a comment - That is Great, Many thanks!

            Minh Tran added a comment -

            Dear atlassian-service454091850,

            This has been merged and resolved in 5.10.x.

            Best regards,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - Dear atlassian-service454091850 , This has been merged and resolved in 5.10.x. Best regards, Minh Tran Confluence BugMaster Atlassian

            Hi,

            I am hitting this issue with Confluence 5.9.7. Was this solved on new version of Confluence? Thanks!

            Jean-Claude Passy added a comment - Hi, I am hitting this issue with Confluence 5.9.7. Was this solved on new version of Confluence? Thanks!

            I think we are affected by this bug too. In the single issue version of the macro only (the table display does not have this problem) the issue type icon fails to render. We are operating JIRA and Confluence from the same server behind an Apache reverse proxy with the typical configuration (using NamedVirtualHosts to map two sub-domains to the correct ip and port for JIRA and Confluence respectively, and yes per doc ProxyPreserveHosts is ON). JIRA and Confluence have an application link through a separate Tomcat connector on different ports than the Apache reverse proxy; this ensures they are not reaching out to the name-server just to share resources. In the application link, our addresses look like: http://127.0.0.1:8081/things. This is how the icon attempts to render (and fails) for the client, though strangely the icon link correctly uses the display URL for the app link. See a screenshot of the result below:

            Please advise if you can, we'll submit a support ticket as well as this issue is cosmetically problematic. We migrated from cloud and are running 6.0.0-OD-2016.03.1-0006.

            Ryan Knopf added a comment - I think we are affected by this bug too. In the single issue version of the macro only (the table display does not have this problem) the issue type icon fails to render. We are operating JIRA and Confluence from the same server behind an Apache reverse proxy with the typical configuration (using NamedVirtualHosts to map two sub-domains to the correct ip and port for JIRA and Confluence respectively, and yes per doc ProxyPreserveHosts is ON). JIRA and Confluence have an application link through a separate Tomcat connector on different ports than the Apache reverse proxy; this ensures they are not reaching out to the name-server just to share resources. In the application link, our addresses look like: http://127.0.0.1:8081/things . This is how the icon attempts to render (and fails) for the client, though strangely the icon link correctly uses the display URL for the app link. See a screenshot of the result below: Please advise if you can, we'll submit a support ticket as well as this issue is cosmetically problematic. We migrated from cloud and are running 6.0.0-OD-2016.03.1-0006.

            Hi Victor and Mayur

            I disabled the 2 modules and faced some issues:

            • Macro browser does not open when typing '{jira' and hitting enter but an empty jira macro is shown which causes an error after saving the page
            • typing {jira:key=someissue-1}

              will be handled as wiki markup in edit mode

            • and cosmetically: icon in macro browser is still wrong

            The first point is a nogo for us so we won't use the workaround although it fixed the icons.

            Hope to get the fix soon.

            Cheers Liesa

            ProjectteamA added a comment - Hi Victor and Mayur I disabled the 2 modules and faced some issues: Macro browser does not open when typing '{jira' and hitting enter but an empty jira macro is shown which causes an error after saving the page typing {jira:key=someissue-1} will be handled as wiki markup in edit mode and cosmetically: icon in macro browser is still wrong The first point is a nogo for us so we won't use the workaround although it fixed the icons. Hope to get the fix soon. Cheers Liesa

            Hi Victor,

            After disabled 2 modules "jira(jira-xhtml)" & "jiraissues(jiraissues-xhtml)" we have not seen any issue.

            Regards,
            Mayur Ingale.

            Mayur Ingale added a comment - Hi Victor, After disabled 2 modules "jira(jira-xhtml)" & "jiraissues(jiraissues-xhtml)" we have not seen any issue. Regards, Mayur Ingale.

            Hi mayingale1149006286

            Are you facing any problem after disabling the modules?

            Generally speaking, if the 2 modules are disabled then the "view issues" button on Confluence side will not be rendered properly.

            Cheers,
            Victor

            Victor Teoh (Inactive) added a comment - Hi mayingale1149006286 Are you facing any problem after disabling the modules? Generally speaking, if the 2 modules are disabled then the "view issues" button on Confluence side will not be rendered properly. Cheers, Victor

            Occurring on Confluence 5.9.2 Server Instance for us. Preview mode loads the right icons, but after publishing, icons use the application url.

            Joseph Than (Inactive) added a comment - Occurring on Confluence 5.9.2 Server Instance for us. Preview mode loads the right icons, but after publishing, icons use the application url.

            Mascha added a comment -

            Same happens in the JIRA Report Blueprint (Change log) for all generated links on the created pages - see Screenshot.

            Mascha added a comment - Same happens in the JIRA Report Blueprint (Change log) for all generated links on the created pages - see Screenshot.

            Mayur Ingale added a comment - - edited

            I have got a solution may be workaround on this issue.

            Open a "JIRA Macros" from Confluence Manage Addons, Expand the "JIRA Macros" modules & disable "jira(jira-xhtml)" & "jiraissues(jiraissues-xhtml)". Now my JIRA issue url & Issue type icons are rendering according to display URL.

            Mayur Ingale added a comment - - edited I have got a solution may be workaround on this issue. Open a " JIRA Macros " from Confluence Manage Addons, Expand the "JIRA Macros " modules & disable " jira(jira-xhtml) " & " jiraissues(jiraissues-xhtml) ". Now my JIRA issue url & Issue type icons are rendering according to display URL.

              jmcarthur James McArthur (Inactive)
              kyong Kok Yan Yong (Inactive)
              Affected customers:
              38 This affects my team
              Watchers:
              57 Start watching this issue

                Created:
                Updated:
                Resolved: