On this page:

Problem

During the Analyze Changes phase of Jira Server/Data Center to Cloud migrations or Jira Cloud to Cloud deployments, the following error occurs for a custom field:

Reason

There is a managed (also might be a locked) custom field that doesn’t exist on your destination Jira Cloud site. These types of custom fields are automatically created and managed by the Jira Software, Service Management, and Mobile Connect applications.

Solution

You’ll have to make manual configuration changes in order to resolve the issue and continue the migration or recreate the deployment. To resolve the problem, you can:

• exclude the field from the source configuration,

• create the field in the destination,

• create Service Management SLA-type custom fields, or

• enable Jira Mobile Connect for fields created by it.

See details of the possible resolutions listed below.

Exclude the field from the source configuration

Ensure the field is not part of the source migration/deployment scope in the source Jira. For example, Jira Software projects sometimes refer to Service Management fields. For server-to-cloud migrations, you can use Power Admin for better troubleshooting where exactly the field is used.

Create the field on the destination

If the custom field is created by Jira Software or Service Management, go to your destination Jira Cloud site. There, install the missing application and create a sample project or add the custom field manually. After rerunning the migration analysis or recreating the deployment, everything should be in order.

Create Service Management SLA-type custom fields

SLA-type custom fields are fields created by Jira Service Management automatically when you add an SLA to a service project. Alternatively, you can manually create them by adding an SLA in Project settings > SLAs. However, you cannot directly create these custom fields from the Custom Fields list in Jira. Learn more about creating custom fields.

Each service project comes with a set of default SLAs and their corresponding SLA-type custom fields already created.

When you’re migrating service projects referring to SLA-type custom fields, you need to have the same custom fields in the destination as well. If the destination Jira Cloud site doesn’t contain these custom fields, you’ll see the error “Managed custom field isn’t found on the destination“. Then, you need to create these SLA-type custom fields on the destination with the source field names to be able to accomplish the migration.

To resolve the error, create the missing SLA-type custom fields by:

• creating a sample service project, or

• creating SLAs in your destination project matching the missing SLA-type custom fields

In the first case, Jira Service Management will automatically create the following SLA-type custom fields: Time to close after resolution, Time to resolution, Time to first response, and Time to review normal change. If the migration is giving you errors about any of these fields, then you can use the sample service project creation option to work around the problem.

However, if the migration is looking for other SLA-type custom fields, you’ll need to create your own SLAs with the source SLA-type fields' names in the destination. This will automatically create the corresponding SLA-type custom fields.

To create new SLAs in an existing service project on the destination, you need to go to the Project settings > SLAs and type a new SLA name, as shown in the screenshot below. Afterward, you’ll have a custom field with that name in your Jira Cloud site.

Open

Creating destination SLAs when migrating service requests

If the service management projects you’re migrating contain requests with SLAs, you’ll have to create the exact same SLAs on the destination if not present already. In this case, the source and destination SLAs must have the same names and same configuration. Otherwise, the requests won’t be migrated correctly.

Case-sensitivity by SLA-type field names

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 https://appfire.atlassian.net/wiki/spaces/DCMCMT/pages/609127303 document.

Enable Jira Mobile Connect

If the custom field is created by Mobile Connect, go to your destination Jira Cloud site. Create a sample Software project. Then, navigate to Project settings > Summary > Settings > Jira Mobile Connect, click Enable, and the field will be created automatically. You can disable Mobile Connect again after that. Rerun the migration analysis or recreate the deployment, and everything should be in order.