Summary

Check what to do when your Jira Cloud Migration Assistant (JCMA) migration fails to migrate Advanced Roadmaps (AR) plans due to missing Project Version dependencies.

Overview

The error message below will surface when some project versions related to an AR plan are out of sync within Jira; they may not exist anymore. The <plan-id> and <plan-name> refer to the project id and name.

ERROR CROSS-PROJECT-DATA project-import We couldn't import Plan <plan-id> because of 1 missing dependencies: Project Version '<version-name>'

When a project version is deleted from the project, that deletion doesn't propagate to the AR plans.

Reopening the AR plans on the Exclusion Rules allows Jira to fetch the most up-to-date data related to its versions.

Solution

The solution will depend on the version of the Advanced Roadmaps installed.

Advanced Roadmaps 8.15 and higher - following Jira's 8.15 upwards

 Just by opening the Exclusion Rules UI, the releases that have been excluded will be updated on the database.

(Option 1) Reach the page directly

1. Navigate to the following URL, replacing the <plan-id> with the one mentioned in the error log message and <jira_base_url> with the Jira on-prem base URL.
   

   <jira_base_url>/secure/PortfolioPlanView.jspa?id=<plan-id>#settings/setExclusionRules

2. Retry the migration.

ERROR CROSS-PROJECT-DATA project-import We couldn't import Plan 55 because of 1 missing dependencies: Project Version 'Version Name'.

(Option 2) Navigate through the UI

1. Open the AR Plan.
2. Click Configure.
3. Click Exclusion Rules

Advanced Roadmaps 3.29 and lower - available until Jira 8.14.x

Advanced Roadmaps 3.29 and lower don't have the Exclusion Rules UI, so the solution is to delete the invalid Project Versions entries from the database.

Make sure to delete only the entries from your JCMA error log file.

Let's use the error message below as an example (make sure to replace the Project Version IDs with the ones present on your log files):

ERROR CROSS-PROJECT-DATA project-import We couldn't import Plan 17 because of  4 missing dependencies: 
Project Version 19200, Project Version 19301, Project Version 19404, Project Version 19418.

1. Stop Jira Server.
2. Take a backup from the database.

3. Delete the entries referenced in the log:

   DELETE FROM AO_D9132D_EXCLUDED_VERSIONS WHERE VERSION IN (19200, 19301, 19404, 19418);

4. Start Jira and run a new migration plan in JCMA.