Migration fails using JCMA due to Cascading Custom Field with different Context

Kasturee

We were attempting a migration of 4 Jira Projects from Jira Server to Cloud to our sand-box environment using JCMA.  The migration was failing on JCMA on one of the Jira Projects due to there being a different context set for that project on a cascading custom field. The 3 Jira Projects migrated successfully and only the one project with the different context set had failed.

Is anyone aware of there being any limitations on JCMA regarding different contexts set for custom fields and what is the workaround for a successful migration?

JCMA V1.6.8

Example of Error Message: "customfield_10207: Specify a valid option 'id' for Risk Category. This caused 3 other items to fail."

Majo Francis _MicroGenesis Techsoft_

Hi @Kasturee 

I doubt if it was the field context which caused it..

Do you see any disabled option with the option name such as 'XYZ'  for the 'Risk Category' field ??

 

You should see the option name in the beginning of your error log.

"[XYZ] customfield_10207: Specify a valid option 'id' for Risk Category. This caused 3 other items to fail."

 

While I am not sure about the recommended solution, I feel we should temporarily enable the disabled options before migration.. Probably a limitation of JCMA.