Details
-
Bug
-
Resolution: Fixed
-
High
-
None
-
JCMA - 1.6.9
-
None
-
11
-
Major
Description
Issue Summary
Jira Cloud Migration Assistant for Jira is getting stuck when running migration
Steps to Reproduce
Install Jira server v7.6.1. Create Advanced Roadmaps plans for the customer.
Try a migration using JCMA.
Expected Results
Migration success
Actual Results
Migration failed for the customer with the below error:
"CrossProjectDataMigrationResult":{
2 "Error":{
3 "Error":"PluginTask.Failure",
4 "Cause":"java.lang.NoSuchMethodError: com.atlassian.jira.project.ProjectManager.getProjectsByArgs(Ljava/util/Collection;)
5Ljava/util/Collection; (StackTrace=java.lang.NoSuchMethodError: com.atlassian.jira.project.ProjectManager.getProjectsByArgs(Ljava/util/Collection;)
6Ljava/util/Collection;ntat com.atlassian.jira.migration.workers.AbstractCrossProjectDataProcessor.exportCrossProjectData(AbstractCrossProjectDataProcessor.kt:68)ntat
7com.atlassian.jira.migration.workers.AbstractCrossProjectDataProcessor.process(AbstractCrossProjectDataProcessor.kt:44)ntat
8
Workaround
Update the least supported version from 7.6.0 to 7.10.0
Related issues
This issue has caused some incomplete migration issues in support for cross project data, when the dark features from How to migrate all boards and filters with the Jira Cloud Migration Assistant (JCMA) Atlassian Cloud were enabled. Migrations will not fail, but they will be incomplete and will not include cross-project filters and boards.
Details
This behavior is seen when Jira is on a supported version (7.10+), with Advanced Roadmaps installed, and JCMA v1.7.1.
The same errors around exportCrossProjectData are seen in these cases. However, the migration plan does not fail - it finishes as Incomplete and cross-project boards/filters do not get migrated. JCMA ignores these flags, and will skip cross-project filter and board migration:
2022-12-10 17:27:51,869+0000 pool-53-thread-16 WARN [c.a.j.m.e.software.board.RapidViewExportService] Skipp exporting multi-projects board Advertising Systems under exportMode PROJECT_DATA
In at least one of the cases the customer was running Jira v8.20.x. So the issue is related to this bug.
Upgrading to JCMA 1.7.4+ resolves the incomplete migration issue.