Hello,
I'm currently migrating from a DC installation to a cloud installation for JIRA, we're using scriptrunner and I had to do the initial JQL keyword sync described here: https://docs.adaptavist.com/sr4jc/latest/features/scriptrunner-enhanced-search/scriptrunner-enhanced-search-jql-keywords-synchronization
However as the page indicates, this takes a long time to finish. But it's only needed once, and then any "new" issues that are added shouldn't need another manual sync, but it should be done automatically.
My question here is can I just do the initial synchronization on an empty JIRA cloud instance? That way when I migrate all my issues, I don't need to do the initial sync that could potentially take weeks to finish?
If not, is there a threshold of tickets I need to have in my instance before I can do the initial sync? We're planning to migrate in phases (a handful of jira projects first, then another handful, then the rest, etc...). Would we need to wait till all the migrations are done before we do that initial synchronization?
Thank you all in advance.
Pierre
Hi @Pierre Ibrahim,
No, you cannot perform the initial sync before any issues are there. You should be able to perform that initial sync after your first migration completes.
I would assume you will need this in your production migration eventually. Just run the initial sync after you complete the first phased migration on production. Test this in your test environment(s) beforehand so you have a clear idea of the actual sync time, so you can document this in your runbook and communicate any potential delays to your users up front (or plan your migration accordingly).
Hope this helps!
Replying here because phased migration always sparks interesting questions and is a topic of great interest.
It sounds like the earlier response covered your question about ScriptRunner syncing. I hope it worked for you!
Since you’re planning a phased migration, I'll just add that Backbone Work Sync (another Marketplace app) can also help, as it keeps issues (and Jira data) on DC and Cloud instances in sync throughout the transition. This allows you to avoid long downtimes or timing mismatches across instances. Here's a quick write-up on how that works.
I’m super interested, though, in understanding how you’re planning this migration and the challenges you’re running into. If you’re up for a quick chat, please book a slot on my Calendly or email me at usohail@k15t.com.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.