Facing an error from server to cloud

Question

Ajay_9y9r89 · Answer

@Sandhya, you can use the  Darkfeature com.atlassian.jira.migration.skip.invalid.workflow.rule to  ignore these JCMA checks.

unknown · Answer

Maybe this article will help you.
In brief, Atlassian recommends to re-create your workflows manually, because "Non-native Jira Workflow Functions are currently not supported" by JCMA.

Looks like you should manually switch your project to simpler workflows (that will not contain any non-native conditions, validators and post-functions) before migration, migrate it using JCMA and then switch the migrated project to manually crafted original workflows in Cloud Jira.

Such a fancy automation :)

Ulas Falcioglu · Answer

Hello Liam,

We used the JCMA for the migration from the test server to the cloud and got the same error. Some projects couldn't be migrated.

2022-04-04 09:51:56.124 ERROR ... project-export The workflow: [......] transition: [Resolve Issue] has unsupported custom field reference in config hidFieldsList for workflow rule validator [FieldsRequiredValidator]. Double-check the workflow rule for missing config values or references.

What can we do here?

Thanks

Ulas