Versions Compared

Old Version 10

changes.mady.by.user Comala Publishing for Confluence Cloud

Saved on

compared with

New Version 11

changes.mady.by.user Julver Petrova

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 ✅

Тeam-managed Software projects

✅

❌

Jira Service Management projects

❌

Boards

✅

Filters

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

Users

✅

Groups

⚠

Group membership will not be transferred

App data

❌

Note
Deploying

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.