Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,874
Community Members
 
Community Events
176
Community Groups

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

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

3 answers

1 accepted

0 votes
Answer accepted

Hello @fjgonzalez

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

Best regards,

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

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

0 votes
Jimmy Van Atlassian Team Jan 23, 2022

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:

  1. 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.
  2. Run the Database Integrity Checker to check and fix any inconsistencies in the Server.
  3. 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 Community Leader May 25, 2022

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 Atlassian Team May 26, 2022

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events