• Products
  • Documentation
  • Resources

How boards and filters are migrated

The Jira Cloud Migration Assistant lets you migrate all boards and filters to cloud. This includes:

  • Boards created from multiple projects

  • Boards from an existing saved filter

  • All shared filters - a filter can have shared access with :

Shared access with

Description

Private

The filter is private and can only be viewed and edited by the owner and Jira admins.

User/Group/Project

The filter is shared with a user, group, or project. Depending on the permissions granted, users can view or edit the filter.

Any logged-in user

The filter is shared with all users on your Jira instance.

Anyone on the web

If a filter is Shared with anyone on the web, this allows public access to certain information on your site. If you want to prevent people who aren’t logged in from viewing this information and limit access to your logged-in users, either:

  • Single project boards and filters created and shared with projects selected for migration would be automatically migrated regardless of the options chosen.

What are the ways to migrate boards and filters migration

In the Jira Cloud Migration Assistant, you can choose one of the following options:

Option

Migration behavior

Example

Only filters and boards shared to selected projects
Both single and cross-project boards created on or shared with the projects you've selected for migration.

What’s migrated

What’s not migrated

  • All filters and boards created or shared with your selected projects


 

  • Single project filters shared with:

    • Public/private, or to certain users and groups

    • Non-migrating projects

  • If you've selected Project A and Project B for migration, then all boards and filters created or shared to these two projects would be migrated.

  • Boards and filters shared with public/private, users, groups, or with a non-migrating Project C would be migrated.

All filters and cross-project boards
All filters (both single and cross-project) and cross-project boards, irrespective of their shared access.

  • All filters and cross-project boards, regardless of their shared access

 

  • Single project boards created on

    • non-migrating projects.

To migrate these boards, include the relevant projects in your migration.

  • If you’ve selected Project A and Project B, then all filters and cross-project boards will be migrated regardless of their shared permission.

  • Single project boards created on project C, which is not included in migration would not be migrated. To migrate these boards, you’ll have to migrate Project C.

None

  • No boards and filters will be included for migration.

(Some boards and filters are migrated even when this option is selected. Known issue: MIG-1654)

 

 

Test migrations

For a test migration or User Acceptance Testing (UAT), we recommend that your test cloud site isn't part of the production organization. This is to ensure smooth migration of the relevant cross-project boards and filters.

More information and support

We have a number of channels available to help you with your migration.

 

Additional Help