Details
-
Bug
-
Resolution: Obsolete
-
Highest
-
None
-
None
-
None
-
207
-
Severity 3 - Minor
Description
Issue Summary
When using the DFs (com.atlassian.jira.migration.export.shared.filters, com.atlassian.jira.migration.export.all.filters, com.atlassian.jira.migration.export.multiprojects.boards) to run a migration for all projects, the first project will have the multiple errors like the one below:
ERROR ABC project-import We couldn't import Board 'Board name' because of 1 missing dependencies: Project XYZ. Check the reasons for the missing dependencies on your server site.
The errors will be in the first project that is being migrated, it doesn't even need to be a filter that is referring to multiple projects.
However, if I check the cloud instance after the migration is done, we can find the "Board name" under the project "XYZ", so the error was misleading.
As the public page mentions:
All boards and filters will get migrated at the beginning of the first plan but their location may not as expected. Nevertheless, project location will be reassigned as migrations progress through the plan or multiple plans.
It seems that the boards are imported before the projects are in the cloud, and this is causing the errors.
Steps to Reproduce
- Enable the dark features mentioned in the summary
- Create a migration plan for multiple projects that have boards
Expected Results
Migration is successful without errors
Actual Results
The first project that is being migrated will have errors like:
ERROR ABC project-import We couldn't import Board 'Board name' because of 1 missing dependencies: Project XYZ. Check the reasons for the missing dependencies on your server site.
Workaround
How to migrate all boards and filters with the Jira Cloud Migration Assistant (JCMA)
Attachments
Issue Links
- blocks
-
MOVE-72090 Loading...
- is caused by
-
-
- is related to
-
-
-
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- relates to
-
-
-
-