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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a few dozen projects of varying sizes and complexities that need to be migrated from an old Jira server to a new Jira Data Center server.
Would it be possible to create a snapshot, deploy that into the new JDC instance, then create another snapshot with just the issues that changed since the last snapshot was created as deploy that to call it "migrated"?
This would give us the time needed to do the migration without a days long downtime for the service.
Hi @Tony Rice
I'm not sure if this is technically feasible using CMJ specifically - I'd probably recommend contacting the vendor directly, or checking out their documentation.
But, it's not something I'd necessarily try either during a migration - unless there's a good reason to do it, such as the DC Launch being in the future for all users simultaneously.
I'd recommend:
Or, if you must do this - I'd look to create a (real-time) link between the Issues in Server and DC, and allow this to manage Issue updates, etc - until you're ready to complete each move across to DC.
I've seen this done before using either...
But, some of these options might not offer support for all Issue components, such as the Issue History - which is why I'd usually avoid the need to do this unless absolutely necessary.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.