We’re renaming ‘products’ to ‘apps’

Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change

How to migrate boards and filters

The Jira Cloud Migration Assistant lets you migrate boards and filters to cloud. This includes boards created from multiple projects, boards from existing saved filters, and shared filters.

Before migration, it's important to understand how filters can be shared:

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

The filter is publicly accessible. To limit access to logged-in users, either:

  • Change the filter's permissions

  • Remove public access to these filters. Learn more about anonymous user access

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

Migration options

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

Option 1 : 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

All filters and boards created or shared with your selected projects

What’s not migrated

Single project filters shared with:

  • Public/private, or to certain users and groups

  • Non-migrating projects

Example

  • 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 not be migrated.

Option 2 : All filters and cross-project boards

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

What’s migrated

All filters and boards created or shared with your selected projects

What’s not migrated

Single project boards created on non-migrating projects. To migrate these boards, include the relevant projects in your migration.

Example

  • 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.

Option 3 : None

What’s migrated

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)

More information and support

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



Still need help?

The Atlassian Community is here for you.