Details
-
Bug
-
Resolution: Not a bug
-
Medium
-
None
-
None
-
None
-
5
-
Minor
Description
Issue Summary
JCMA fails to migrate boards owned by users that don't have permission to browse the project being migrated. The error is misleading as it will indicate that boards is a Cross-project boards
JCMA pre-migration summary logs show:
Cross-project board Boards that reference multiple projects are not supported via migration. This board will not be migrated. If you require this board, re-create the board in your cloud site. To pull out the JQL for board filters, run SQL queries from this page: https://confluence.atlassian.com/jirakb/troubleshooting-errors-and-non-migrated-entities-with-the-jira-cloud-migration-assistant-1021239878.html
Steps to Reproduce
- Have a single project board be owned by a user with no 'Browse Project' permissions for the project associated with the board
- Migrate the project that contains the board using JCMA
Expected Results
JCMA should migrate that project and board
Actual Results
JCMA finishes, but board will not be migrated and listed as a 'Cross-project' board in pre-migration logs
Workaround
Make sure to board owner has permissions to browse project associated with board