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

JIRA Issues macro links to application URL rather than display URL - the search link uses the application URL.

      Application links have both an application URL, the URL by which the app connects on the backend (eg. http://jira.localhost), and a "display URL", the link displayed to the user (eg. https://jira.company.com").

      Currently this doesn't work with the jiraissues macro, because:

      • If I use the "application URL" parameter (eg. "http://jira.localhost/sr/..."), I get results, but the hyperlink of the search is then wrong.
      • If, as a workaround, I try to use the "display URL", I get an message telling me "This table displays contents from an external source. The contents will be displayed as HTML. If you trust the security of this source, you can display the original formatting and avoid this warning by creating an Application Link to this JIRA instance".

      As for fixing this, I suggest: when rendering the search link, examine the search XML URL, and if it begins with an applink URL, substitute the applink's display URL.

        1. display.png
          display.png
          52 kB
        2. jira_issue3.png
          jira_issue3.png
          69 kB
        3. result.png
          result.png
          116 kB
        4. wrong image url.png
          wrong image url.png
          20 kB

            [CONFSERVER-29182] JIRA Issues macro links to application URL rather than display URL - the search link uses the application URL.

            exactly - thank you sometimes it's hard to find the correct issue

            Oliver Straesser added a comment - exactly - thank you sometimes it's hard to find the correct issue

            Hi oliver.straesser, it sounds like you're running into CONF-36648. You can add yourself as a watcher on that ticket and you'll be notified of any updates.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - Hi oliver.straesser , it sounds like you're running into CONF-36648 . You can add yourself as a watcher on that ticket and you'll be notified of any updates.

            Hi

            we installed the JIRA Macro 5.6.11 Add-on and have different App Links as Display URLS configured.

            But the Icons of the JIRA Issues aren't loaded, because the app link is used to link the image url.

            Should I open a new case, or did I missed a configuration.

            Cheers
            Oli

            Oliver Straesser added a comment - Hi we installed the JIRA Macro 5.6.11 Add-on and have different App Links as Display URLS configured. But the Icons of the JIRA Issues aren't loaded, because the app link is used to link the image url. Should I open a new case, or did I missed a configuration. Cheers Oli

            Thanks for pointing this out Jeff! I've actually spoken with the Application Links people and I have some more information.

            In Confluence 5.3 and JIRA 6.1 (Applinks 4.0) the Application URL will be automatically set to the Base URL of the instance. You will still be able to update the Display URL of the link.

            As we know from tickets like this one, that is not always a viable configuration, and customers often need to create the link with a URL that is not the Base URL, to bypass proxies, SSL etc.

            The current workaround in that case is to set the BaseURL of the applications to the URL you want to create the link with, then create the link. The Application URL for both applications will be their BaseURL. You can then set the BaseURL back to the correct user-facing URL, and edit the Display URL of the application link.

            This issue is being tracked here for Confluence: CONF-32611

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - - edited Thanks for pointing this out Jeff! I've actually spoken with the Application Links people and I have some more information. In Confluence 5.3 and JIRA 6.1 (Applinks 4.0) the Application URL will be automatically set to the Base URL of the instance. You will still be able to update the Display URL of the link. As we know from tickets like this one, that is not always a viable configuration, and customers often need to create the link with a URL that is not the Base URL, to bypass proxies, SSL etc. The current workaround in that case is to set the BaseURL of the applications to the URL you want to create the link with, then create the link. The Application URL for both applications will be their BaseURL. You can then set the BaseURL back to the correct user-facing URL, and edit the Display URL of the application link. This issue is being tracked here for Confluence: CONF-32611

            For people whose applinks have a differing display URL: Atlassian completely removed that ability in JIRA 6.1+ and recent Confluences, in the name of 'simplification'. Please vote on JRA-36989 if you need it.

            Jeff Turner added a comment - For people whose applinks have a differing display URL: Atlassian completely removed that ability in JIRA 6.1+ and recent Confluences, in the name of 'simplification'. Please vote on JRA-36989 if you need it.

            tolive added a comment -

            That's done it, thanks for the clarification!

            tolive added a comment - That's done it, thanks for the clarification!

            Hi Tristan,

            The fix for this wasn't landed on time by the time we released 5.3.1 bug fix version for Confluence 5.4.1. You can now download and install 5.3.2 which has the fix. Sorry for the late response.

            Nguyen

            Nguyen Dang added a comment - Hi Tristan, The fix for this wasn't landed on time by the time we released 5.3.1 bug fix version for Confluence 5.4.1. You can now download and install 5.3.2 which has the fix. Sorry for the late response. Nguyen

            tolive added a comment -

            Can anyone shed any light on why this still wouldn't be working on Confluence 5.4.1 with JIRA Macros 5.3.1?

            We're using JIRA 5.2.9, does that need to be upgraded to some particular version in order for the fixed JIRA Macros to work? Seems irrelevant, since I can get a table of issues to render, they just have incorrect links.

            tolive added a comment - Can anyone shed any light on why this still wouldn't be working on Confluence 5.4.1 with JIRA Macros 5.3.1? We're using JIRA 5.2.9, does that need to be upgraded to some particular version in order for the fixed JIRA Macros to work? Seems irrelevant, since I can get a table of issues to render, they just have incorrect links.

            tolive added a comment -

            We upgraded to Confluence 5.4.1 and JIRA issues are still linking to the application URL instead of the display URL. Clicking the link then sends the user to http://localhost:8081/browse/... which doesn't work.

            I checked the JIRA Macros add-on version and it is 5.3.1. Do we have to do something different in order for the link to use the display URL instead of the application URL? Or maybe the fix is missing from JIRA Macros 5.3.1?

            The only thing I got to work was selecting multiple issues and choosing "Total issue count" under display options. This links correctly using the display URL. Single issue or Table formats are not working.

            tolive added a comment - We upgraded to Confluence 5.4.1 and JIRA issues are still linking to the application URL instead of the display URL. Clicking the link then sends the user to http://localhost:8081/browse/ ... which doesn't work. I checked the JIRA Macros add-on version and it is 5.3.1. Do we have to do something different in order for the link to use the display URL instead of the application URL? Or maybe the fix is missing from JIRA Macros 5.3.1? The only thing I got to work was selecting multiple issues and choosing "Total issue count" under display options. This links correctly using the display URL. Single issue or Table formats are not working.

            For us too. But got another one. The Team Calendar ist still using the Application Url instead of the DisplayUrl.

            David Zahorsky added a comment - For us too. But got another one. The Team Calendar ist still using the Application Url instead of the DisplayUrl.

              ndang Nguyen Dang
              97bf41494e76 Jeff Turner
              Affected customers:
              27 This affects my team
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: