Description

This page explains:

Migration support details for the app content from server/DC to cloud
Differences between the server/DC and cloud version of the app

Pre-requisites

Ensure to install Create on Transition for Jira, version 7.7 or newer, and Jira Cloud Migration Assistant on the server/ DC instance.

Migration process

Install (and configure) Create on Transition for Jira on your cloud instance.
Install Jira Cloud Migration Assistant on the server/DC instance from which you intend to migrate the Create on Transition for Jira workflow and app configurations.
Use System > IMPORT AND EXPORT > Migrate to cloud to navigate to the migration screen where you can migrate global app configurations, workflow configurations, and/or users and groups, as required. For more information, refer to this page.

Differences between Server/DC and Cloud versions of the app

The following table lists the feature differences between the Server/DC and Cloud versions of the app.

Parameter/Feature	Server/DC	Cloud

Parameter/Feature	Server/DC	Cloud
Features	Supported post functions: Create Issue(s) Creat Sub-task(s)	Supported post functions: Create Issue Create Subtask Update Issue Supported validators: Conditioned Validator
Conditions based on substitution variables	JQL supported for validators	JQL not supported for validators. Jira expressions are supported instead.
Copy issues in epic	Supported	Not supported
Copy attachments	Supported	Supported with a limitation of user not being able to add attachments during workflow transitions
Conditions for subtask default handling	Supported	Not supported
Issue fields Due date offset Target issue status (Update Issue only) Remote link(s) - Link types Optional rules Regular expression pattern (for Conditions & Configuration > Create multiple issues)	Supported	Not supported All Confluence links are copied to the issue being created or updated as web links. The following result in a broken image in the issue being created or updated: Any media (image or GIF etc..) embedded in the original or parent issue's comments. Any non-image media files or attachments such as GIF etc., in the description or environment fields. Create multiple issues in the Conditions & configuration tab does not support the use of regular expressions. Copy attachments and Copy links are not supported while creating multiple issues or subtasks.

In the Cloud version, you notice that the features supported by Update on Transition for Jira are combined with Create on Transition for Jira.

When a user has configured the Acting user field in the post functions, this field is not migrated and the user has to manually update it.

Limitations

It is recommended that the administrator creates the following field entities if they have not been migrated by JCMA:

Components
Fix versions
Affected versions
Labels
Reporter
Assignee
Watchers

Substitution variables processing

Custom fields

When substitution variables are used to set custom fields in the source instance, the following representations are not currently supported in workflow post function migrations:
- entry_customfield_<issue key>
- values_customfield_<custom field id>
- values_customfield_<issue key>(entry)
- transition_customfield_<custom field id>
In the add custom field section, if the server/ DC instance has substitution variables, then they will not be migrated. Only selected values will be set.

Others

When the following fields are defined using substitution variables in the source instance, they are not processed and are copied as-is to the target instance:

JQL query
Acting user

Problem reporting

If you experience any problems or behavior changes that are unexpected, refer to Help and open a ticket with us. This helps us identify and prioritize fixes and improvements.