Supported configuration elements

On this page:

1 Supported configuration elements in cloud-to-cloud deployments
- 1.1 Specifics of deploying boards and filters

Supported configuration elements in cloud-to-cloud deployments

The table below lists the configuration CMJ Cloud is able to deploy in the cloud-to-cloud use case.

Supported

Not yet supported

Supported with some specifics

Configuration		CMJ Cloud

Configuration		CMJ Cloud
Projects
	Jira company projects
	Тeam-managed projects
	Jira Service Management (JSM) projects	Only partial migration is available. See the full list of currently supported JSM configurations.
Agile boards
App data
Custom fields
Dashboards
Events		Custom events cannot be created yet. They can only be referenced if they already exist on the destination instance.
Field Configurations
Filters		Only the filters associated with boards in the deployment scope are moved. JQL isn’t transformed.
Groups		Group membership will not be transferred
Issues
Issue Link Types
Issue Types
Priorities
Project Categories
Schemes
	Field Configuration Schemes
	Issue Security Schemes
	Issue Type Screen Schemes
	Notification Schemes
	Permission Schemes
	Screen Schemes
	Workflow Schemes
Screens
Sprints
Statuses
Resolutions
Roles
Users
Workflows

Specifics of deploying boards and filters

When deploying boards and filters from a Jira Cloud site, CMJ Cloud is able to:

add the ones that don’t exist in the destination Jira Cloud, and
modifies the existing ones on the destination Jira Cloud if differences are detected.

However, when migrating from Jira Server to Cloud, Jira Server boards, filters, and sprints are only added to Jira Cloud. For such migrations, the boards, filters, and sprints existing in the destination aren’t modified in any way.