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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

JCMA error about missing dependencies - need translation and assistance please

Rob Horan Community Leader May 25, 2022

Assume a log file filled with lines like this one, anonymized of course.

2022-05-24 19:05:39.428 WARNING KEY project-import We couldn't import Issue Link 'Epic-Story Link' (from KEY-1234 to PRJ-5678) because of 1 missing dependencies: Issue PRJ-5678. Check the reasons for the missing dependencies on your server site.

Does this mean that the JCMA took its ball and went home because the PRJ project wasn't present?

If so:

  • Does this mean that there is a requirement for some projects to be in place before others can be migrated?
  • If so, how do we know what those will be up front so that we can prepare?
  • What if these projects all have dependencies on each other?
  • Does this mean we cannot import projects that are linked to others that might be left behind as part of a cleanup?

1 answer

2 votes

Hi Rob,

This information previously posted in the community might help -

Otherwise, I suggest opening a support ticket for additional assistance.



Hi @Jordan Chitwood ,

This is a Japanese page, and not part of the community.  It would be great if it were part of the standard documentation.

Being part of the Japanese documentation, it didn't come up in a standard search.

This is actually not the first time I found the Japanese documentation to be superior to the standard site.  Are you guys holding back?  :) 

In any case, that error is for fix versions.  Is there a generic document for this kind of error? 

This migration has a move ticket, and the errors were reported over a week ago, and there has been no response.

Hi @Rob Horan ,

Great feedback on the documentation. I do not have any additional documentation to add at the moment. I would suggest opening a Migration Support ticket for additional assistance.



Like Rob Horan likes this
Rob Horan Community Leader Jun 06, 2022

Yeah... we just got a little bit of an answer on our move ticket after well over a week of silence. 

Based on the number of articles I've seen, I would guess there are many variations of this dependency error - enough so that it might be good to have a genericized KB about how to deal with them.  Just my $0.02 but it would be very stress relieving.

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events