nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Field 'Sprint'. Check the reasons for the missing dependencies on your server site.

fjgonzalez

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

Accepted answers

desarrollo

Hello @fjgonzalez

Try creating a sprint in the source instance. Having a open sprint in the source instance could fix the error.

Best regards,

All comments

desarrollo

Hello @fjgonzalez

Try creating a sprint in the source instance. Having a open sprint in the source instance could fix the error.

Best regards,

fjgonzalez

Thank you @desarrollo

paolo.bolla

I have the same problem but having a Sprint active on source don't fix the error.

Jimmy Van

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:

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.

Rob Horan

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.

Jimmy Van

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".

Bram_9c60dd

It's a bit disturbing that this still hasn't been resolved in the migration tool.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

migration

jira-software

jira-software-cloud