Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-372

JIRA keeps dead links to Confluence pages after migration and space import

XMLWordPrintable

    • 28
    • Severity 3 - Minor

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

      Symptoms

      After a migration, a full JIRA export is imported into a new instance, which means Confluence must be imported space by space.

      Any existing links on JIRA tickets to Confluence pages (Mentioned In links) are still to the old page ID so will not load.

      Testing

      First Approach

      I imported customer JIRA and Connie data and my dev instance (https://adiallo.jira-dev.com) and was able to reproduce the issue. In the JIRA issue, I was seeing the Page Failed to load under the Issue Links opposite the mentioned in option. That's the same way the customer is seeing it.

      Second Approach

      1. I created a JIRA issue in another dev instance (https://stan.jira-dev.com/browse/BUR-5) and mentioned in and Confluence page (https://stan.jira-dev.com/wiki/display/ds/M%2Cz%3E%2Cxz%3Exz) and the display was fine from both side.
      2. I exported JIRA and Confluence from https://stan.jira-dev.com and imported it into: https://adiallo.jira-dev.com.
      3. After a successful import and reindex, the same error appear in the JIRA Issue (https://adiallo.jira-dev.com/browse/BUR-5): Page Failed to load and from Confluence side it throws: JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

          Form Name

            [MIG-372] JIRA keeps dead links to Confluence pages after migration and space import

            Ali BenCafu added a comment -

            Update on the development of a solution to address this issue and fix Jira and Confluence links on migrated products from Server or DC to Cloud:

            • We are working on a solution on Admin Hub to enable admins to fix links after migration from Server/DC to Cloud, which will be released in the second half of the calendar year 2023.
            • While building the solution on Admin Hub, we want to ensure that we enable Solution Partners to fix links on behalf of the customers they work with, and for that, we will launch an API-based solution for Solution Partners to fix links, which will be released before the end of the first half of the calendar year 2023.
            • For customers who don’t work with Solution Partners, and until we launch a solution for Solution Partners to fix links, customers and Solution Partners can open a support ticket, and our Migration Support Engineers will provide support on fixing links in Jira and Confluence migrated from Server/DC to Cloud.
            • To improve the Atlassian Migration Support Engineers’ experience and have an internal robust solution for fixing links, we will be launching an internal solution for Migration Support Engineers to use internally to fix links on migrated Cloud products, which will be released in February or March of 2023.

            If you have (or soon will have) links that are not working in Confluence or Jira migrated from Server/DC to Cloud:

            • If you are working with a solution partner, they can open a support ticket, and Atlassian Migration Support will assess your case and provide support accordingly.
            • If you are not working with a solution partner, you can open a support ticket, and Atlassian Migration Support will assess your case and provide support accordingly.

            Note: The solution we are working on will cover Jira and Confluence links in Jira and Confluence products that are migrated from Server/DC to Cloud.

            If you have any questions or feedback please feel free to comment on this ticket and we will get back to you.

            Ali BenCafu added a comment - Update on the development of a solution to address this issue and fix Jira and Confluence links on migrated products from Server or DC to Cloud: We are working on a solution on Admin Hub to enable admins to fix links after migration from Server/DC to Cloud, which will be released in the second half of the calendar year 2023. While building the solution on Admin Hub, we want to ensure that we enable Solution Partners to fix links on behalf of the customers they work with, and for that, we will launch an API-based solution for Solution Partners to fix links , which will be released before the end of the first half of the calendar year 2023. For customers who don’t work with Solution Partners, and until we launch a solution for Solution Partners to fix links, customers and Solution Partners can open a support ticket, and our Migration Support Engineers will provide support on fixing links in Jira and Confluence migrated from Server/DC to Cloud. To improve the Atlassian Migration Support Engineers’ experience and have an internal robust solution for fixing links, we will be launching an internal solution for Migration Support Engineers to use internally to fix links on migrated Cloud products, which will be released in February or March of 2023 . If you have (or soon will have) links that are not working in Confluence or Jira migrated from Server/DC to Cloud: If you are working with a solution partner, they can open a support ticket , and Atlassian Migration Support will assess your case and provide support accordingly. If you are not working with a solution partner, you can open a support ticket , and Atlassian Migration Support will assess your case and provide support accordingly. Note: The solution we are working on will cover Jira and Confluence links in Jira and Confluence products that are migrated from Server/DC to Cloud. If you have any questions or feedback please feel free to comment on this ticket and we will get back to you.

            Patrick van der Rijst added a comment -

            This happens using the Confluence Cloud Migration Tool as well.

            Patrick van der Rijst added a comment - This happens using the Confluence Cloud Migration Tool as well.

            Valerii added a comment -

            Comment for notification. I have the same problem. 

            Valerii added a comment - Comment for notification. I have the same problem. 

            Andy Cleff added a comment -

            /me waves hand, jumps up and down in agreement - this is a huge value to end users... 

             

            sorry I have only one vote to give...

            Andy Cleff added a comment - /me waves hand, jumps up and down in agreement - this is a huge value to end users...    sorry I have only one vote to give...

            MattS added a comment -

            My feeling is that this is not a Low priority problem!

            MattS added a comment - My feeling is that this is not a Low priority problem!

            Alfonso Leiva [ServiceRocket] added a comment -

            This is interesting. This issue was created on December 9th, 2014. 22 months old... and really no one has complained about this on this issue?

            We moved our customer's JIRA and Confluence tools from Server to Cloud this last weekend and we are facing this problem now.
            We opened a Support Ticket here https://support.atlassian.com/servicedesk/customer/portal/23/JST-225578 and it gets closed saying that we should be following this current issue to "consolidate our efforts as opposed to having several engineers working on one overall issue". So my question is, is really an engineer working on this?

            The official way to move to the Cloud is to import JIRA and then, due to the 200MB limit, move Confluence spaces one by one. And there's no warning saying that we are going to lost all the references from JIRA to Confluence and it seems that is not something that is part of Atlassian main priority by now.

            I guess it's ok to reopen the support ticket and work only for our case, right?

            Alfonso Leiva [ServiceRocket] added a comment - This is interesting. This issue was created on December 9th, 2014. 22 months old... and really no one has complained about this on this issue? We moved our customer's JIRA and Confluence tools from Server to Cloud this last weekend and we are facing this problem now. We opened a Support Ticket here https://support.atlassian.com/servicedesk/customer/portal/23/JST-225578 and it gets closed saying that we should be following this current issue to "consolidate our efforts as opposed to having several engineers working on one overall issue". So my question is, is really an engineer working on this? The official way to move to the Cloud is to import JIRA and then, due to the 200MB limit, move Confluence spaces one by one. And there's no warning saying that we are going to lost all the references from JIRA to Confluence and it seems that is not something that is part of Atlassian main priority by now. I guess it's ok to reopen the support ticket and work only for our case, right?

            MattS added a comment -

            p.s. Connie is the pet name for Confluence

            MattS added a comment - p.s. Connie is the pet name for Confluence

              06eb947e2f93 Łukasz Halicki
              jrobison1 JordanA
              Affected customers:
              22 This affects my team
              Watchers:
              41 Start watching this issue

                Created:
                Updated:
                Resolved: