@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.
https://docs.adaptavist.com/sr4jc/latest/scriptrunner-migration/platform-differences
https://scriptrunner-docs.connect.adaptavist.com/jiracloud/scripted-fields.html
Thanks
V.Y
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
More details at https://docs.adaptavist.com/sr4js/latest/scriptrunner-migration/migrating-to-or-from-cloud/migrate-from-scriptrunner-for-jira-cloud-to-server
Cheers,
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.