Versions Compared

Version Old Version 5 New Version Current
Changes made by

Andrea Pedrollo

Andrea Pedrollo

Saved on

Key

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

Since v7.1.0 (compatible with Jira 9) and 8.1.0 (compatible with Jira 10) Multi-Level Cascading Select has been integrated on Jira Cloud Migration Assistant.

Before we start

Note

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.

You Due to Atlassian’s limitations, you are required to unset set your MLCS default value to none to complete the migration.

If you keep your default value set, the error [JCMA 104] will be thrown during the pre-migration check:

2025-02-17 10:53:29.043877587 ERROR PROJ project-export Custom field type: com.sourcesense.jira.plugin.cascadingselect:multi-level-cascading-select for Custom Field 'AAA MLCS' is not supported. [JCMA 104].

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

...