The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events