-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
JCMA - 1.12.9
-
Minor
Issue Summary
During the migration of a custom field value (associated with an app) from Data Center to Cloud using JCMA, an error occurs that prevents progress beyond the pre-migration checks. However, if the default values are removed, the migration completes successfully.
This is reproducible on Data Center: 
Steps to Reproduce
- Create a server app implementing Forge listener and app custom fields
- Create an app custom field in your Jira Server setting a default value for it.
- Create a new migration ensuring Data preparation preflight check is run
Expected Results
Since JCMA doesn't support the migration of custom fields associated with the app, it should not block the preflight check.
Actual Results
The error below occurs during the preflight data preparation phase.
The below exception is thrown in the atlassian-jira.log file:
Exporting entity Custom Field Default Value xxxxx failed com.atlassian.jira.migration.export.framework.ExportException: Custom field type: com.xxxxx.jira.plugin.cascadingselect:multi-level-cascading-select for Custom Field 'AAA-mlcs-1-fm-dc' is not supported at com.atlassian.jira.migration.export.core.customfield.CustomFieldValueParser.parseValue(CustomFieldValueParser.kt:180) at com.atlassian.jira.migration.export.core.customfield.CustomFieldValueParser.parseValue$default(CustomFieldValueParser.kt:86) at com.atlassian.jira.migration.export.core.customfield.CustomFieldDefaultValueExporter.parseDefaultValue(CustomFieldDefaultValueExporter.kt:78)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|