We couldn't import Issue because of 1 missing dependencies: Custom Field 'Sprint'
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When trying to run the Jira Cloud Migration Assistant (JCMA) to migrate from Server to Cloud, the migration plan fails and the following message appears stating there are possible issues with the field Sprint:
2021-12-06 14:20:40.787 ERROR <Project Key> project-import
We couldn't import Issue <Project Key>-<Issue Number> because of 1 missing dependencies:
Custom Field 'Sprint'. This caused <Number of Ocurrences> other items to fail.
Check the reasons for the missing dependencies on your server site.Environment
This message applies to the Jira Cloud Migration Assistant (JCMA).
- From Server to Cloud
Cause
Dependency issues between migrated projects or inconsistencies.
Solution
Please make sure to follow all the steps below:
- Check if the field Sprint is added to the screens in the screen schemes associated with the affected projects, and make sure to add it in case it is missing.
- Run the Database Integrity Checker to check and fix any inconsistencies in the Server.
- Afterward, if the issue persists, try to migrate the affected projects individually. Bringing them all at once in a single Migration Plan could be causing dependency issues.
Last modified on Dec 8, 2021
Powered by Confluence and Scroll Viewport.