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
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
@khushboo_puri If you are referring to JMCF Calculated Custom Fields, we had to recreate them as simple number fields in the cloud. Then, during our first migration test, we created automation rules to replicate the calculations. Now, you can export the automation rules and reimport each time you perform an import, but the chance of the field IDs changing is very probable. So, keep track of the new IDs and simply update the rules.
We had a lot and once we had our process down, we were able to make he changes within a few hours. It just all depends on the number of fields.
Hope this helps.
Hi @khushboo_puri You need to rewrite all scripted field in JIRA Cloud. Automatic migration between Server/Data Center and Cloud does not exist due to the differences in the programming model and the API.
I’m assuming you are referring to Scripted fields from Scriptrunner. If that is the case, all scripts from your Jira Server/DC must be rewritten in Jira Cloud.