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
In my environment we have two Jira Server instances (2x Jira version 8.5).
Instance A should be left untouched for the moment.
Instance B will "lift and shift" to the cloud.
At the moment Instance A and B are heavily using Issue links (just normal application links to the second instance).
My question: how will Instance A know that all application links that currently point to the on-prem Instance B will have to point to the cloud?
As only Instance B will be migrated I have no clue how to "notify" Instance A.
Adjusting 23697 manually is not an option - I guess?!
Thanks in advance!
Hey @bschmi !
To ensure I got the full scenario for your use case, have you already decided on the migration method, process to be more precise, that you'll be using for this lift&shift instance B migration?
I was checking the Jira Site import documentation, If there are links that need to be mapped in cloud section and this might also help:
At this step, you may see a list of URLs for Atlassian server sites. To make sure links point to the new Jira Cloud site instead of the old server site after you migrate:
In both methods, Jira Site import & Jira Migration Assistant, as a first step, post instance B migration to the cloud, you will need to set up a new Application link between instance A, and the instance B newly in the cloud, that will be similar to the current app links you have set up, and you can guide after the steps mentioned in this article.
Once that is done, the apps will know how to communicate one with the other.
The second step post-migration will be to review the links that are still pointing to the old instance and correct them, and for that our support team can help and run a query on the cloud database to confirm all the links that are still pointing to the old instance, and if/how these can be fixed, for the majority of links, until a permanent fix is implemented (we are working on a tool for this), the team can help and run a database update to update old URL with new URL when by replacing the site name the link will be fixed.
As these are reciprocal, once the links are updated in Jira instance B, these should be updated also in Jira instance A.
I would highly recommend you to perform a test migration and reach out to us by raising a case from https://support.atlassian.com/contact/#/ > select Migration support from the second drop-down and our team will review your exact use case for links post-migration and ensure you got all the details and the impact during the test.