Find answers to questions regarding app migration.
This page helps you resolve common issues that may arise when migrating Extension for Jira Service Management from Data Center to Cloud.
For detailed instructions on settings related to JCMA, consult Atlassian Cloud migration guide and Atlassian documentation.
To learn details about the migrated data, it’s recommended to download app migration logs via Actions > View logs. The logs contain warnings and errors detected during migration. The sections below cover the most common problems and describe how to fix them.
If the app migration fails due to a timeout, you can re-run the migration within 12 days of the original attempt. During a re-run, all the already-migrated projects are skipped.
This can happen when a migration plan includes app data for a project that has not yet been migrated by Jira Cloud Migration Assistant. To resolve the issue, either:
Could not resolve request type(s) for project <id>: DC IDs <ids>. These entries were skipped.
This problem may occur when a project was migrated successfully, but one or more request types couldn’t be matched to a Cloud equivalent and were excluded from the migrated configuration. The DC request type IDs listed have no corresponding Cloud request type ID.This means the request type wasn’t migrated by Jira Cloud Migration Assistant.
First, ensure the affected request types have been migrated to Cloud. Next, you can:
The resolved request types will be included in the re-migrated configuration.
Could not resolve issue link type(s) for project <id>: <names>. These entries were skipped.
This message indicates that the project was migrated successfully, but one or more issue link type configurations couldn’t be matched to a Cloud equivalent and were excluded from the migrated configuration. This typically happens when a link type exists in DC but has no counterpart in the Cloud instance.
First, create the missing issue link type(s) in the Cloud instance. Next, you can:
Once re-migrated, the configuration will reflect the new link types.
Could not resolve group(s) for project <id>: <names>. These entries were skipped.
This message indicates that the project was migrated successfully, but one or more SLA visibility groups couldn’t be matched to a Cloud group and were excluded from the migrated configuration. The group may not have been migrated to Cloud or may have a different name.
Create the missing group(s) in the Cloud instance. Then, you can:
This process will re-migrate the configuration by using the now-available groups.
No configuration to migrate for project <id>, skipping.
This is expected when a project uses all-default Request Details View settings in DC (no custom fields, attachments, issue links, or SLA visibility configured). In this case no action is needed.
If you expected this project to have custom settings, check the preceding warnings in the log for unresolved entities (link types, groups, SLA metrics). Once the missing entities are created in Cloud, either reconfigure the project manually or create a new migration plan for the affected project(s) with the App data only scope.
Could not fetch SLA metrics for project <id> (API error) — SLA visibility settings will be skipped for this project. Re-run migration to retry, or configure SLA visibility manually.
This message indicates an API error which occurred while retrieving SLA metric definitions for the Cloud project. It means that SLA visibility settings weren’t migrated for this project.
If you can’t find the answer you need in our documentation, raise a support request. Include as much information as possible to help our support team resolve your issue faster.
Apps documentation