Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-34998

Updating Application Link cause rendering problem: "Error rendering macro 'jira' : Unable to locate JIRA server for this macro. It may be due to Application Link configuration"

XMLWordPrintable

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

      When creating a mirror image for testing purposes of our Jira instance, we then need to delete the application link to the Production instance of Confluence.
      This then breaks the application link between our Production Jira and Production Confluences as well.
      The only solution that has worked is to delete then re-add the application links on both sides (same URL as was there in the first place).
      However:
      Jira macros in Confluence display "Error rendering macro 'jira' : Unable to locate JIRA server for this macro. It may be due to Application Link configuration".

      Steps to fix:
      1. Edit page
      2. Edit macro
      3. The macro still contains the issue number. Click the magnifying glass, re-find the correct issue.
      4. Save page.

      Since the macro is saving the issue number, and the Jira link is the same (just re-adding it), I shouldn't have to go through every Confluence page containing a Jira macro just to re-find information that's already populated in it.
      Ideal behavior is for the macro to take the existing search query it contains and search in the new application link for it, THEN issue an error if it can't find it.

        1. Jira Issue 1.jpg
          Jira Issue 1.jpg
          39 kB
        2. Jira Issue 2.jpg
          Jira Issue 2.jpg
          32 kB

          There are no Sub-Tasks for this issue.

              Unassigned Unassigned
              a0b5091b82fd Sabina H.
              Votes:
              4 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: