Hello Team,
After performing a migration of some software projects, the migration assistant returns the following error:
ERROR SM project-import We couldn't import Issue SM-433 because of 1 missing dependencies: Custom Field 'Sprint'. This caused 19 other items to fail. Check the reasons for the missing dependencies on your server site.
After checking a bit I could see that the tickets related to sprints were not imported. Can someone help me?
Thanks in advance,
Francisco Gonzalez
Hello @fjgonzalez
Try creating a sprint in the source instance. Having a open sprint in the source instance could fix the error.
Best regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same problem but having a Sprint active on source don't fix the error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For anyone searching in the future - https://confluence.atlassian.com/cloudkb/we-couldn-t-import-issue-because-of-1-missing-dependencies-custom-field-sprint-1095247814.html is a helpful article.
Namely:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jimmy Van this page seems to be specific to the Sprint field but this missing dependency error message can go far beyond that. Is there a more generic approach to troubleshooting these kinds of errors?
For an example, please look at the question I raised here: https://community.atlassian.com/t5/Atlassian-Migration-Program/JCMA-error-about-missing-dependencies-need-translation-and/qaq-p/2038450
I have concerns about the implications of this error, outlined on that page.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rob Horan ,
I linked this article and followed up as it's a very specific issue, caused by a specific bug.
You may like to check out https://confluence.atlassian.com/jirakb/troubleshooting-errors-and-non-migrated-entities-with-the-jira-cloud-migration-assistant-1021239878.html for more other errors that can be independently troubleshooted.
With respect to the implications of the error, the specifics are best discussed with our team. Please raise a new ticket at https://support.atlassian.com for "Migration Support".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.