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

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: サーバーと Data Center のみ。この記事は、サーバーおよび Data Center プラットフォームのアトラシアン製品にのみ適用されます。

要約

As of version 1.6.6, the Jira Cloud Migration Assistant app supports the migration of Advanced Roadmaps (AR) Plans. AR Plans related errors might surface during a JCMA plan execution.

This error is one of the potential ones an admin may face while migrating data from a Jira Server/DC instance along with AR Plans over to an Atlassian Jira Cloud site.

環境

  • JCMA 1.6.6 and higher
  • Jira Server/Data Center 7.6.0 and higher
  • Advanced Roadmaps (confirm your version before applying one of the workarounds outlined below)

エラー

This error message below will surface when some project versions related to an Advanced Roadmap plan may be out of sync within Jira, i.e., they may not exist anymore. The <plan-id> and <plan-name> refer to the project id and name.

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


Possible Root Cause

When one deletes a project version from within the project, that deletion doesn't propagate to the AR plans. Reopening the AR plans, on the Exclusion Rules, makes Jira fetches the most up-to-date data related to its versions.

Solution 1 (Advanced Roadmaps 8.15 and higher - which follows Jira's version from 8.15 upwards)

URLs

  1. Go to a web browser and execute the following URL making sure to replace the <plan-id> with the one mentioned on the error log message and <on-prem-jira-base-url> with the Jira on-prem base URL.

    <on-prem-jira-base-url>/secure/PortfolioPlanView.jspa?id=<plan-id>#settings/setExclusionRules

    Error log:

    2022-08-05 06:42:19.288266 ERROR CROSS-PROJECT-DATA project-import We couldn't import Plan 55 because of 1 missing dependencies: Project Version 'Version Name'. This caused 1 other items to fail. Check the reasons for the missing dependencies on your server site.

    URL:

    • https://myjirasite.com/secure/PortfolioPlanView.jspa?id=55#settings/setExclusionRules
  2. Retry the migration of the failed Advanced Roadmap plan

手動

Open the AR Plan -> Configure -> Exclusion Rules (on the left side). Just by opening the Exclusion Rules UI, the Releases that have been excluded will be updated on the database.

Solution 2 (Advanced Roadmaps 3.29 and lower - which is available for Jira version until 8.14.x)

Manual DB deletion

Advanced Roadmaps 3.29 and lower do not have the Exclusion Rules UI - so the solution is to delete the invalid Project Versions entries from the AO_D9132D_EXCLUDED_VERSIONS table directly 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 own log files):

2022-08-16 22:27:24.621458 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. This caused 3 other items to fail. 
  1. Apply the workaround (stop Jira first, as you'll be changing data directly on the database):

    DELETE FROM AO_D9132D_EXCLUDED_VERSIONS WHERE VERSION IN (19200, 19301, 19404, 19418);
  2. Start Jira and run a new migration plan in JCMA.


If you're on PostgreSQL, make sure to enclose the table and column names in double quotes.

最終更新日 2022 年 8 月 19 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.