You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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

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

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


Server / Data Center

Cloud

MappingWhat to distinguish?




Post function parameters




ModeMode(tick)

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.
  • 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 TypeIssue Type(tick)

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.

ProjectProject(tick)

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.

SummarySummary(tick)

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.

DescriptionDescription(tick)
Additional fieldsFields(tick)
Issue linksIssue links(tick)
Additional Options
(error)In Jira Cloud, there are no Temporary fields, so there are no additional options.
Conditional executionConditional execution(tick)
Run asRun as(tick)In the Cloud, there are available only user fields.