...

Reason

...

You can also hit the error “Managed custom field isn’t found on the destination“ if the source and destination SLA fields have different capitalization of the letters in the name. For example, if you have a source SLA field called Time to resolution and a destination field called TIME TO RESOLUTION, they won’t be mapped to each other. In this case, you either have to use the Customize mapping feature to map both fields to each other or to create a new destination SLA with the exact name and capitalization matching the source field.

For other information related to migrating service projects, check also the /wiki/spaces/DCMCMT/pages/609127303 document.

Enable Jira Mobile Connect

...