After migrating from Server to Cloud (both JIRA and Confluence), the running the JIRA Macro Repair fixes the links from Confluence to JIRA, but not from JIRA to Confluence, which continue to point to the server.
Does anyone know the cause and how to fix?
The cause is that the XML file that uploads JIRA is still pointing at the old Confluence server.
We actually just addressed this issue recently when migrating a client from Server to Cloud.
When performing a migration from one Server instance to another, the issue is relatively easy to solve as a simple "find and replace" of the old domain name with the new domain name will suffice. The issue with moving to cloud is that all of the links that point to Confluence are in the form of https://<domainname>/pages/viewpage.action?pageId=<contentID>. When you move to Cloud, all of the ContentID's are rewritten.
I was able to fix this issue, but it is a pretty technical process. If you aren't comfortable working with shell scripts, the DB and Rest API, fixing the issue is going to be quite challenging. If you're up for it I can attempt to describe the process, but I don't know how well I can explain it in this format.
Have you already performed the migration? Once it's been done, there isn't a way that I've found to perform the fix. I was told by Atlassian support that they have some steps to perform after an instance has been migrated, but it isn't "technically" support.
The solution to this is not too difficult if you understand the data structure of the integration and a bit of scripting experience.
Note you only need to do this if the Page ID's are going to change (e.g. when you import a Space individually).
The easiest way to perform this task is to iterate over the imported Jira Issues like follows - for each Jira Issue imported (e.g. from JQL search):
The following resources should be referenced:
I recommend using Python for this, as it is quick to sketch out the code, I'd say also use the following to simplify the amount of work needed:
If you were migrating Server-to-Server, I would recommend dumping the CONTENT table and saving on authenticating all those REST Requests, but in this sort of case (Cloud), we would leave the script running for hours/days etc. and this would be a 'bleed-over' migration activity, which doesn't block people using the system.
You are facing some known migration related issues:
If you are affected by above issues you can open a ticket with Atlassian support in https://support.atlassian.com in order to have the links fixed.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs