You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
This information previously posted in the community might help - https://ja.confluence.atlassian.com/cloudkb/we-couldn-t-import-project-version-because-of-missing-dependencies-project-jcma-error-1101926685.html
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.
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.