We couldn't import Project Version because of <Number_of_Occurrences> missing dependencies

Still need help?

The Atlassian Community is here for you.

Ask the community

For Atlassian eyes only

This article is Not Validated and cannot be shared with customers.

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

The following documentation offers guidance on resolving the project import error associated with Project Versions that can't be imported to the Cloud due to missing dependencies.

Overview

When trying to run the Server to Cloud Migraiton using the Jira Cloud Migration Assistant (JCMA), the migration plan fails and the following message appears in atlassian-jira.log:

ERROR <Project_Key> project-import We couldn't import Project Version <Version_Name> because of <Number_of_Occurrences> missing dependencies: Project <Project_Key>. This caused <Number_of_Issues> other items to fail. Check the reasons for the missing dependencies on your server site. 

The project uses entities from another project that aren't migrating, which results in the missing dependency. Fix Versions are specific to each project. This issue can be resolved within a project by following these recommended steps: Add or create the <Version_Name> for the appropriate project. Then, disassociate the project version that links with other projects. After that, re-associate it with the newly created version through a bulk operation.

Fix Project version dependencies error

  1. To resolve this issue, identify the affected issues that have the Project version <Version_Name> by running this JQL (Jira Query Language):

    project = <Project_Key> and fixversion = '<Version_Name>'
  2. Then, perform a bulk update on the issues to remove the FixVersion from other projects and assign them to their respective ones.
  3. If the issue persists or if the above JQL yields no results, run the below query on the Jira Server database to locate the affected issues: 
    select p.id project_id_issue, pv.project project_id_version, (p.pkey || '-' || i.issuenum) as key, i.summary, pv.id version_id, pv.vname version_name from jiraissue i 
    inner join project p on i.project = p.id 
    inner join nodeassociation na on na.source_node_id = i.id 
    inner join projectversion pv on pv.id = na.sink_node_id 
    where association_type = 'IssueFixVersion' 
    and p.pkey in ('PROJECT_KEY') 
    and p.id != pv.project;
  4. Follow step 2 again to bulk update to remove the FixVersion against the above result.


Last modified on Apr 19, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.