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

            Martin Trneny added a comment -

            Hi Atlassian,
            your status is fine but can you confirm that your JIRA macro repair "feature" caused the CONF-44240? If yes why this issue isn't link to that issue?

            Martin

            Martin Trneny added a comment - Hi Atlassian, your status is fine but can you confirm that your JIRA macro repair "feature" caused the CONF-44240 ? If yes why this issue isn't link to that issue? Martin

            Martin Trneny added a comment -

            Hi all,

            please be careful. We were affected by JIRA macro repair. See https://jira.atlassian.com/browse/CONF-44240. Your Confluence cloud pages could be modified in a disaster way!

            Martin Trneny added a comment - Hi all, please be careful. We were affected by JIRA macro repair. See https://jira.atlassian.com/browse/CONF-44240 . Your Confluence cloud pages could be modified in a disaster way!

            Saida Aslanova added a comment -

            Hi,
            What about server version? When it will be fixed?
            On 5.9.12 we faced the same error.

            Saida Aslanova added a comment - Hi, What about server version? When it will be fixed? On 5.9.12 we faced the same error.

            Thales Santos added a comment -

            Hi, is there any idea of which version this is going live?

            Thales Santos added a comment - Hi, is there any idea of which version this is going live?

            Richard Atkins added a comment -

            Other space import data fixes that we need to do include https://jira.atlassian.com/browse/CONF-34994 - there are probably several other areas where the imported content isn't linked correctly, due to the space export linking to resources (in the case of the linked issue, users; and in this case, jira issue keys and application links). Longer term, we need to come up with an approach that we can make it easy to solve these other issues easily.

            Richard Atkins added a comment - Other space import data fixes that we need to do include https://jira.atlassian.com/browse/CONF-34994 - there are probably several other areas where the imported content isn't linked correctly, due to the space export linking to resources (in the case of the linked issue, users; and in this case, jira issue keys and application links). Longer term, we need to come up with an approach that we can make it easy to solve these other issues easily.

            Doug added a comment -

            We are migrating about two dozen spaces to a new Confluence instance. This bug is causing us to fix the links on three JIRA instances and two Confluence instances during the migration. Our project plan for the entire migration will end up being almost 8 hours, including verifying a sample of links on each instance were fixed. Plus a few months of preparation work for the new Confluence instance.

            Doug added a comment - We are migrating about two dozen spaces to a new Confluence instance. This bug is causing us to fix the links on three JIRA instances and two Confluence instances during the migration. Our project plan for the entire migration will end up being almost 8 hours, including verifying a sample of links on each instance were fixed. Plus a few months of preparation work for the new Confluence instance.

            Daniel Sánchez added a comment -

            Our instance is beaing affected by this issue but on a migration from one instance of OnDemand to another, both with Jira and Confluence. I see this issue was created on Oct 2013 and it doesn't seem to have any recent updates... I recommend you to check on that priorization because this issue can really mess up your whole documentation system.

            Daniel Sánchez added a comment - Our instance is beaing affected by this issue but on a migration from one instance of OnDemand to another, both with Jira and Confluence. I see this issue was created on Oct 2013 and it doesn't seem to have any recent updates... I recommend you to check on that priorization because this issue can really mess up your whole documentation system.

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

                Created:
                Updated:
                Resolved: