Versions Compared

Old Version 8

changes.mady.by.user Rosen Marinkov

Saved on

compared with

New Version Current

changes.mady.by.user Stanley Neychev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:

Table of Contents
minLevel1
maxLevel6
include
outlinefalse
indent
styledefault
exclude
typelist
class
printabletrue

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 with some specifics

Configuration

CMJ Cloud

Jira Work Management projects

✅

Jira Software company projects

  • Project configuration ✅

  • Boards

and Sprints ✅

  • ✅

Тeam-managed Software projects

✅


❌

Jira Service Management

projects ❌

(JSM) projects

⚠

Only partial migration is available. See the full list of currently supported JSM configurations.

Boards

✅

Filters

⚠
Only the filters associated with boards in the deployment scope are moved. JQL isn’t transformed.

Events

⚠
Custom events cannot be created yet. They can only be referenced if they already exist on the destination instance.

Users

✅

Groups

⚠

Group membership will not be transferred

App data

❌

Note
Deploying

Specifics of deploying boards

,

and filters

, and sprints

When deploying boards , and filters , and not closed sprints 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.

When However, when migrating from Jira Server to Cloud, however, 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.