/
JCMA Essential Requirements and Guidelines

JCMA Essential Requirements and Guidelines

This page provides valuable points regarding the migration of Multi-Level Cascading Select field context and issue data, from Jira Data Center to Jira Cloud.

Pre-Migration Requirements

  • App version: v7.1.1 for Jira 9.x, v8.1.3 for Jira 10.x, v9.0.1 for Jira 11.x

  • There are no known cleanup or configuration steps required before migration.

  • Validation checks are built into the migration helper.

  • Do not forget to set your MLCS default values to none before migration. More about this here:Jira Cloud Migration Assistant.

Migration Failing at 99%

  • In some cases, during the migration you could see your MLCS migration failing at 99%

    image-20260605-102302.png

  • The error is related to an incorrect processing by Atlassian of our completed chunk notification. Since this is a minor issue and, although it can be alarming, it does not affect the migration itself.

  • The migration process works as expected, and the data is correctly transferred among the instances. Therefore, after evaluating the risks, we decided to avoid introducing any changes that could compromise the stability of the migration.

Post-Migration Actions

After the migration is completed, these are the actions we suggest you perform:

  • Count and compare non-empty MLCS custom field values (using JQL queries in both the instances, Data Center and Cloud).

  • If numbers do not match, you can follow the guide for manual migration (requires ScriptRunner installed in the Data Center instance)

Feature Parity / Limitations