Extension Conversion Mapping
- Daniel Barrow
When migrating from JMWE for Jira Data Center/Server to JMWE for Jira Cloud, some Server extensions will be converted to native Jira Cloud extensions. The native Cloud extensions provide the same base functionality as the JMWE Data Center/Server extensions, but do not include scripting support (for Conditional Execution, for example). It is possible that you could use a JMWE Cloud extension to achieve the same results, but during migration, JMWE Data Center/Server extensions will always be converted to the listed Jira Cloud extensions.
Any JMWE for Jira Data Center/Server extensions not listed in the table below will convert to their equivalent JMWE for Jira Cloud extensions.
Below is a list of extensions that are converted to native Jira extensions when migrating from Jira Data Center/Server to Jira Cloud.
You are viewing the documentation for Jira Cloud.
Extension Type | Extension Name (Data Center/Server) | Extension Name (Cloud) |
|---|---|---|
Post-function | Set issue security level based on current user’s project role (JMWE app) functions.SetIssueSecurityFromRoleFunction | Set issue security level based on user’s project role Class: com.atlassian.jira.workflow.function.issue.SetIssueSecurityFromRoleFunction |
Condition | conditions.NonInteractiveCondition | Hide From User Condition Class: com.atlassian.jira.workflow.condition.RemoteOnlyCondition Key: only-remote-condition |
Condition | Previous Status Condition (JMWE app) conditions.PreviousStatusCondition | Previous Status Condition |
Condition | Separation of Duties condition | |
Validator | Field has been modified Validator | |
Validator | Field has been modified Validator | |
Validator | Field has single value Validator | |
Validator | Field Required Validator | |
Validator | Parent Status Validator | |
Validator | Previous State Validator |