You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Anyone knows how to fix broken issue links after migration of Jira Software to cloud?
I am testing migration one of our Jira Software instances to cloud. After migration and after recreating application links to Jira ServiceManagement and another Jira Software instance, I experience that links only works one-way. From the migrated Jira Software they work fine, but from ServiceManagement and the other Jira Software they are broken.
I guess it is because the Jira Software that has been migrated to cloud has got some sort of new ID, and therefore ServiceManagement and the other Jira Software does not "know" that the cloud instance has replaced the server instance.
Atlassian support is referring to some generic processes that is not specific enough for me to fix the issue:
Any help is highly appreciated.
We had the same issue, but there is a conveniant solution to this: the Atlassian-Support will do this for you. Keep Googling: there is an help article with SQL-queries you have to run on your Server-instance and send these results to the support. They will do the rest. Migrated 18k tickets and 36k pages half a year before, just found 1 or 2 cases where it did not work out.
You have probably already found the relevant information, but for the benefit of others migrating Confluence to cloud, please refer to the information below.
Once the migration of Confluence to cloud completes, the first step is to run the Macro Repair Tool. It may require running the tool several times until the tool does not prompt for any more repairs. Running until you get an error free result is needed to identify and correct the links within the tool's repair scope.
Using the Jira Macro Repair
As of January 2023, there is a know bug you should be aware of concerning the Macro Repair Tool. If you find that the Macro Repair Tool keeps prompting for the same repairs, wait 60 minutes to allow for any backend processing that might be running to complete, and try running the Macro Repair Tool again. If it is still prompting to make the same repair, please open a Support ticket with Atlassian. If you have been working with an Atlassian Cloud Migration Manager (CMM), you would need to follow their instructions on opening a Problem Ticket associated with the migration to get the proper assistance.
CONFCLOUD-73050 - Jira Macro Repair needs to be run multiple times after migration
Once the Macro Repair has completed, or while Atlassian Support reviews the macro repair results as noted above, gather the information in the support document referenced below and open a support ticket \ problem ticket with Atlassian Support to run the Confluence Link Repair. Atlassian will need that information to run their link repairs.
After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance
Please keep in mind that the link repair scripts take a significant amount of time to run, but Atlassian Support will update you when they start the link repairs and usually provide an estimate on when the repairs should complete.
I hope this information is helpful.
Thanks much, Paul. Now, we are not migrating Confluence, only Jira Software, leaving Confluence and Jira ServiceManagement on-premise. Do you have similar information about how to repair broken issue links between:
All help is highly appreciated.
I have some information on Jira link repair, but not much. This was related from one of the Cloud Migration Engineers as part of a similar discussion.
It does not sound like it's helpful, but the Confluence link repair process does make "some" repairs in Jira.
Atlassian is working on enhancements to the post-migration link repair process and they do repair the Jira link as well on a few scenarios as mentioned above.
Also, for the Jira Issues Macro, they have the Jira Macro Repair Tool for Confluence (https://confluence.atlassian.com/confkb/using-the-jira-macro-repair-1084362152.html), which is a tool to fix all Jira Issues Macros after the migration to Cloud.
For reference, you can find a Glossary of Types of Links Resolved by Atlassian Support (https://confluence.atlassian.com/confkb/after-a-successful-server-to-cloud-migration-url-links-are-broken-in-the-new-cloud-instance-1077781093.html).
I hope some of that is helpful.
I had a problem like that and corrected the links over the rest API.
For this to work, you'll need to find a way to map the old linked issues to the cloud once.
In my case, I wrote a script in python, that looked up the issue link in the old on-prem and used a unique identifier (in my case a cf in the target issue). Then on cloud I let the script search for this identifier and changed the false link (cloud source issue) to be corrected to point to the found target issue in cloud.
I hope this will help.