Create issue migration

Same/comparable function available (~95+ % of the common use cases can be mapped)

The function is not available but can be replaced (~75+ % of the common use cases can be mapped)

The function is not available and there is no workaround (yet)

Post function parameters		Notes
Server / DC	Cloud	Notes
Mode	Mode	Mode selector: Server: Two options, we have "Single" and "Multiple". If the second one is chosen, then the Expression field is visible and the user can write there a JQL expression, issue list expression, text list expression, or numeric expression.
Mode	Mode	Cloud: We have several options: single issue, Multiple by text list, Multiple by number, and Multiple by issue list (General parser and Jira Expression).
Issue Type	Issue Type	We have the same options in both of them, but in the Cloud version, we have the option to implement the parser expression in General parser and in Jira Expression.
Project	Project	We have the same options, but in the Cloud version, we also have Seed issue's project, which is useful when we have selected Multiple by issue list.
Summary	Summary	There are some differences in some of the fields, for example, in the Assignee field in the Cloud version we don't have the Automatic option, but the rest of the options are available.
Description	Description
Additional fields	Fields
Issue links	Issue links
Additional Options		In Jira Cloud, there are no Temporary fields, so there are no additional options.
Conditional execution	Conditional execution
Run as	Run as	In the Cloud, there are available only user fields.

If you still have questions, feel free to refer to our support team.