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
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.
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.
This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity. Atlassian:...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event