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

Confluence Space Export/Import Affects JIRA Issue Macro Links

XMLWordPrintable

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

      Atlassian Status as of 12 October 2016

      What had caused this issue?

      The JIRA Issues Macro is used to create links to JIRA issues in Confluence pages. These links contain the identification of which JIRA instance the JIRA Issue Macro then will be referring to.
      This issue occurred as Confluence A and Confluence B do not have the same Application Links configured.
      JIRA Issue Macros' in Confluence B (imported from Confluence A via Space backup) aren't able to render the issues correctly as it is still referring to JIRA instance configured in Confluence A, in which is not configured in Confluence B.

      Resolution for Cloud instances

      The Confluence Cloud importer has been updated to provide a JIRA macro repair feature, in which any broken JIRA macros will be fixed as part of the import.
      For more details on this, please refer to our Import the space content into Confluence Cloud document.

      Workaround for Server instances

      If you're using Confluence Server and you've recently changed domain name, migrated from Confluence Cloud, or merged multiple instances, you may need to relink JIRA issues macros.
      For a workaround of this issue, please refer to the steps outlined in our How to bulk update JIRA Issue Macro to point to a different JIRA instance

      Summary

      Creating a backup of your Confluence Cloud Space to import into another Confluence Cloud instance affects JIRA issue macro with the warning:

      "Unable to locate JIRA server for this macro. It may be due to Application Link configuration."

      Steps to Reproduce

      Export Space XML backup from Confluence A.
      Import the generated XML backup to Confluence B.

      Expected Results

      Contents of the imported Space (JIRA Issue Macro in particular) are rendered successfully.

      Actual Results

      JIRA Issue Macros that exist in the imported space's pages are not rendered. Instead, the following warnings are shown:

      "Unable to locate JIRA server for this macro. It may be due to Application Link configuration."

            [CONFSERVER-31026] Confluence Space Export/Import Affects JIRA Issue Macro Links

            Renata Dornelas made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 188488 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2887001 ] New: CONFSERVER Bug Workflow v4 [ 2980784 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2803696 ] New: JAC Bug Workflow v3 [ 2887001 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Alex Yakovlev (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 210876 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2737475 ] New: JAC Bug Workflow v2 [ 2803696 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2389522 ] New: JAC Bug Workflow [ 2737475 ]
            André K. (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-31026].
              {panel}

            {panel:title=Atlassian Status as of 12 October 2016|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
            h4. What had caused this issue?
            The [JIRA Issues Macro|https://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro] is used to create links to JIRA issues in Confluence pages. These links contain the identification of which JIRA instance the JIRA Issue Macro then will be referring to.
            This issue occurred as Confluence A and Confluence B do not have the same Application Links configured.
            JIRA Issue Macros' in Confluence B (imported from Confluence A via Space backup) aren't able to render the issues correctly as it is still referring to JIRA instance configured in Confluence A, in which is not configured in Confluence B.
            h4. Resolution for Cloud instances
            The Confluence Cloud importer has been updated to provide a *_JIRA macro repair_* feature, in which any broken JIRA macros will be fixed as part of the import.
            For more details on this, please refer to our [Import the space content into Confluence Cloud|https://confluence.atlassian.com/confcloud/import-a-confluence-space-724765531.html#ImportaConfluenceSpace-Step3.ImportthespacecontentintoConfluenceCloud] document.
            h4. Workaround for Server instances
            If you're using Confluence Server and you've recently changed domain name, migrated from Confluence Cloud, or merged multiple instances, you may need to relink JIRA issues macros.
            For a workaround of this issue, please refer to the steps outlined in our [How to bulk update JIRA Issue Macro to point to a different JIRA instance|https://confluence.atlassian.com/display/CONFKB/How+to+bulk+update+JIRA+Issue+Macro+to+point+to+a+different+JIRA+instance]
            {panel}
            h3. Summary
            Creating a backup of your Confluence Cloud Space to import into another Confluence Cloud instance affects JIRA issue macro with the warning:
            {noformat}
            "Unable to locate JIRA server for this macro. It may be due to Application Link configuration."
            {noformat}
            h3. Steps to Reproduce
            [Export Space XML backup|https://confluence.atlassian.com/display/ConfCloud/Export+Content+to+Word%2C+PDF%2C+HTML+and+XML#ExportContenttoWord,PDF,HTMLandXML-ExporttoHTML,XML,orPDF] from Confluence A.
            [Import the generated XML backup|https://confluence.atlassian.com/display/ConfCloud/Import+a+Confluence+Space] to Confluence B.
            h3. Expected Results
            Contents of the imported Space (JIRA Issue Macro in particular) are rendered successfully.
            h3. Actual Results
            JIRA Issue Macros that exist in the imported space's pages are not rendered. Instead, the following warnings are shown:
            {noformat}
            "Unable to locate JIRA server for this macro. It may be due to Application Link configuration."
            {noformat}             		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-31026].
            {panel}
            {panel:title=Atlassian Status as of 12 October 2016|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
            h4. What had caused this issue?

            The [JIRA Issues Macro|https://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro] is used to create links to JIRA issues in Confluence pages. These links contain the identification of which JIRA instance the JIRA Issue Macro then will be referring to.
            This issue occurred as Confluence A and Confluence B do not have the same Application Links configured.
            JIRA Issue Macros' in Confluence B (imported from Confluence A via Space backup) aren't able to render the issues correctly as it is still referring to JIRA instance configured in Confluence A, in which is not configured in Confluence B.
            h4. Resolution for Cloud instances

            The Confluence Cloud importer has been updated to provide a *_JIRA macro repair_* feature, in which any broken JIRA macros will be fixed as part of the import.
            For more details on this, please refer to our [Import the space content into Confluence Cloud|https://confluence.atlassian.com/confcloud/import-a-confluence-space-724765531.html#ImportaConfluenceSpace-Step3.ImportthespacecontentintoConfluenceCloud] document.
            h4. Workaround for Server instances

            If you're using Confluence Server and you've recently changed domain name, migrated from Confluence Cloud, or merged multiple instances, you may need to relink JIRA issues macros.
            For a workaround of this issue, please refer to the steps outlined in our [How to bulk update JIRA Issue Macro to point to a different JIRA instance|https://confluence.atlassian.com/display/CONFKB/How+to+bulk+update+JIRA+Issue+Macro+to+point+to+a+different+JIRA+instance]
            {panel}
            h3. Summary

            Creating a backup of your Confluence Cloud Space to import into another Confluence Cloud instance affects JIRA issue macro with the warning:
            {noformat}
            "Unable to locate JIRA server for this macro. It may be due to Application Link configuration."
            {noformat}
            h3. Steps to Reproduce

            [Export Space XML backup|https://confluence.atlassian.com/display/ConfCloud/Export+Content+to+Word%2C+PDF%2C+HTML+and+XML#ExportContenttoWord,PDF,HTMLandXML-ExporttoHTML,XML,orPDF] from Confluence A.
             [Import the generated XML backup|https://confluence.atlassian.com/display/ConfCloud/Import+a+Confluence+Space] to Confluence B.
            h3. Expected Results

            Contents of the imported Space (JIRA Issue Macro in particular) are rendered successfully.
            h3. Actual Results

            JIRA Issue Macros that exist in the imported space's pages are not rendered. Instead, the following warnings are shown:
            {noformat}
            "Unable to locate JIRA server for this macro. It may be due to Application Link configuration."
            {noformat}
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 [ 2267428 ] New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2389522 ]
            Michael Andreacchio made changes -
            UIS Original: 37

              phnguyen Phong Hong Nguyen
              pgreig Paul Greig
              Affected customers:
              16 This affects my team
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: