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
Next: Root
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
Howdy,
Has anyone been through the exercise of separating Jira Service Desk from a server instance to become a stand-alone JSD server instance? We hit a technical challenge migrating projects from the single Jira Software+Service Desk instance over to a newly built stand-alone JSD instance.
Our problem is caused because the stand-alone JSD target will not include all the add-ons that exist on the source instance. When attempting to migrate a project from the source there are many objects in schemes or custom fields with dependencies on add-ons that do not exist at the target end. This causes errors with migration, whichever technique is used: backup-restore or synchronisation add-on tools.
What are the options to deal with this challenge?
Looking forward to hearing feedback and advice.
Cheers,
Peter Quick
Thanks @Mathis Hellensberg,
I will explore the first option which involves installing all the add-ons, performing the project migration, then cutting the add-ons back.
The second option, using a clone of production, results in the same Atlassian server ID existing on two instances. Instance to instance links are not allows in this scenario as the server can’t link to itself. We need to have issue links from this new instance back to the primary instance.
Cheers,
Peter Quick