Hi 26ff525e2671 ~ JMWE already supports the migration. You can go thru the migration guide (https://appfire.atlassian.net/l/cp/Mkkq52SM)

If you have any questions or find any issues, feel free to reach out to Appfire Support team.

Cheers!

Unfortunately, FieldRequiredValidator, like most JMWE Conditions and Validators, are actually migrated directly by JCMA, without any help from JMWE, to native Jira Cloud Conditions/Validators. Therefore this migration error should be raised with Atlassian.

Hi use a lot of FieldRequiredValidator condition on my workflows. the JCMA does not allow me to migrate anything. What is the solution to this?

error:

2022-11-15 13:37:53.421812 ERROR ICTPRM project-export The workflow: [ICTPRM: ProblemMgmt (Arbeitsablauf)] transition: [Create] has unsupported custom field reference in config fieldKey for workflow rule validator [FieldRequiredValidator]. Double-check the workflow rule for missing config values or references.

The "unsupported custom field" is a "Insight Customfield", which contains the Service, which is affected by an issue. (We do use Insight to manage our service catalogue.)

Thanks,

Chris

All workflow extensions should be migrated - see https://innovalog.atlassian.net/l/cp/X1GhWoex

Do you have any example of workflow extensions that don't migrate?

Some validators, conditions and post-functions migrate, some — don't. Do you have an article or maybe a list of classes which are migrateable and expected to be migrated, and which must be adjusted manually in any case?

Quick update:

We are very pleased to announce the release of our JMWE v7.2.0 which has migration support using Atlassian’s Jira Cloud Migration Assistant (JCMA). This means that the JMWE app now has an automated migration path and can be migrated from Jira Server/Data Center using Atlassian’s Jira Cloud Migration Assistant (JCMA) automation. 

Be aware that JMWE’s Cloud migration using JCMA is currently in beta. For more information about migrating to Jira Cloud using JCMA see Migrating to Jira Cloud using Jira Cloud Migration Assistant.

Quick update:

Our QA team is doing the regression test on our upcoming Cloud release. So far things are looking good. They should be able to wrap up the testing early next week after which, we shall plan to release the Beta version on the cloud.

After the cloud beta release, next will be the server release v7.2.0. This will support the migration on the server/datacenter side. If all goes well, we will release v7.2.0 (initial Beta release) late next week or during the week of 30th May.

Thank you for your patience!

Checking back in here - has the beta version been released? How do we access it in JCMA?

We are currently aiming to release initial support for JCMA in JMWE the week of May 16, barring any last-minute bug. This initial release will be considered as "Beta", just like JCMA itself was initially released as "Beta". 

Hi, Any updates? Thanks!