Issue Summary

Customers currently need to rely on external documentation and manual validation before migrating boards and filters with JCMA. Atlassian’s guidance already documents important prerequisites and common failure conditions for boards, filters, ownership, sharing, JQL validity, and permissions, but these are not fully surfaced as actionable in-product pre-checks with remediation.

Based on the documented guidance, customers may need to validate items such as:

• boards linked to valid filters
• board columns linked to valid statuses
• valid JQL in quick filters
• email addresses / personal data in filters formatted correctly
• shared permissions referring to valid groups
• boards/filters owned by active, valid users
• migration scope alignment for boards referencing projects included in the migration

In addition, the Jira pre-migration checklist states that the migration runner must meet important permission prerequisites, including having Browse Projects on all selected projects for boards/filters migration.

Today, customers may only discover some of these issues after a failed migration, a partial migration, or when boards and filters are missing or inaccessible after migration.

Steps to Reproduce

1. Prepare a Jira Data Center instance with boards and filters intended for migration with JCMA.
2. Introduce one or more documented pre-migration risk conditions, for example:
   • a board linked to a missing/non-existent filter
   • invalid JQL in a quick filter
   • a filter containing improperly formatted email-address-based JQL
   • a board or filter owned by an inactive/deleted user
   • shared permissions referencing an invalid/missing group
   • a board referencing projects outside the selected migration scope
   • run the migration with an admin user that does not have Browse Projects on all selected projects
3. Open JCMA and prepare/run the migration, including boards and filters.
4. Review the pre-migration checks and/or run outcome.

Expected Results

JCMA should include first-class pre-migration checks for board/filter migration readiness and migration-runner permissions, and present clear remediation guidance before a migration starts.

At a minimum, if boards/filters are in scope, JCMA should assess and clearly report whether:

1. Boards are linked to valid filters
2. board columns reference valid statuses
3. Quick filters contain invalid JQL
4. filters contain email-address-based JQL that is not in a supported/quoted format
5. shared permissions reference invalid or missing groups
6. boards/filters are owned by inactive or deleted users
7. boards reference projects outside the migration scope
8. The user running the migration has Browse Projects access to all selected projects
9. The migration-running user meets the documented permission prerequisites relevant to the migration flow

Actual Results

JCMA does not comprehensively detect and surface these documented board/filter and permission prerequisites as actionable in-product pre-checks with clear remediation before migration starts.

Instead, customers may need to:

• discover these requirements from documentation outside JCMA
• investigate issues manually, sometimes with SQL or database-level checks
• encounter failures, partial migrations, or inaccessible/broken boards and filters before understanding the cause

In some cases, the migration may proceed without sufficiently specific readiness feedback, and the customer only discovers the problem during or after migration.

Workaround

Manually follow the KBs

• Preparing boards and filters to be migrated with the Jira Cloud Migration Assistant (JCMA)
• 4. Make sure you have the right permissions [mandatory]