Issue Summary

When performing a Jira cloud-to-cloud migration, the pre-checks will identify affected boards (based on Board Location) with references to invalid filters, resulting in a log like this:

Project Id,Project Name,Board Id,Board Name,Invalid Filter id
12345,Project Name,120,Example Board Name,40543

However, because the board is not accessible due to the invalid filter, it cannot be accessed for deletion or correction. This results in the migration being blocked.

This is reproducible on Data Center: (no)
Jira Cloud currently prevents you from deleting a filter that is currently associated with a board. Reproducing this problem would require manual intervention via the database.

Steps to Reproduce

1. Create a board and set the Location to a project that you will migrate from cloud-to-cloud.
2. Manually invalidate the board by setting the associated filter to an invalid filter ID via the database.
3. Attempt to migrate the project from cloud-to-cloud.

Expected Results

The precheck would provide a path to mitigate the boards that are blocking the migration. Some suggestions:

• An option to delete the offending board
• An option to update the offending board
• An option to clear the Location field for the offending board

Actual Results

A log file is provided with the offending board. Atlassian Support must be engaged to remediate the boards.

Workaround

Contact Atlassian Support.

Suggestion

Allow admins to manage the Orphan Boards. There's an option to manage all filters under "Shared Filters" page, similarly it would be nice to have an option for the “View all boards” page.