Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

If you are coming from the JCMA process, read this!

Error [JCMA 104] JCMA default values migration limitations

Before you begin the migration process, it is important to understand the limitations of Jira Cloud Migration Assistant (JCMA) regarding default values of third-party custom fields.

Due to Atlassian’s limitations, you are required to set your MLCS default value to none in Jira Data Center to complete the migration with JCMA.

if this error screen is displayed during the pre-migration checks:

Screenshot 2025-04-30 alle 11.04.03.png

please check the ZIP file to review the logs. If you encounter the following error: 2025-04-30 07:19:00.022383 ERROR ITS project-export Custom field type: com.sourcesense.jira.plugin.cascadingselect:multi-level-cascading-select for Custom Field 'AAA-mlcs-4-fm-dc' is not supported. [JCMA 104], it means that default values are set in your Jira Data Center instance. To proceed with the process and make sure to migrate your custom field data, Please unset the default values in your custom field page (Configure contextEdit default values). You can set them up again in the Cloud instance once the migration is performed.

For more information on this, visit the related Jira issue: MIG-2180.

This information is also available in our JCMA documentation article: https://sourcesense.atlassian.net/wiki/spaces/SOUS/pages/138379265/Jira+Cloud+Migration+Assistant?atl_f=PAGETREE.

...

After migrating the projects and issues, you can transfer MLCS field values from Server/Data Center to Cloud using the ScriptRunner console. This article outlines the steps to complete the migration:

...