Our new Appfire Documentation Space is now live!
Take a look here! If you have any questions please email support@appfire.com
Feature differences between JMWE Server/DC and Cloud
The main difference in the JMWE for Jira Cloud and JMWE for Jira Server/Data Center extensions is that Server uses Groovy scripting whereas Cloud uses a combination of Nunjucks and Jira expressions.
Below is a list of extensions supported by each product and their equivalents, if applicable.
JMWE Conditions
JMWE for Server/Data Center | JWME for Cloud | Notes |
|---|---|---|
Scripted (Groovy) Condition | Build-your-own (scripted) Condition | JMWE Server uses Groovy scripting, while JMWE Cloud uses Nunjucks expressions and Jira expressions. |
Current Status Condition | Current Status Condition |
|
Related Issues Condition | Linked Issues Condition |
|
Related Issues Status Condition | Linked Issues Status Condition |
|
Hide transition | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud as part of Hide from User. |
Previous Status Condition | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |
Separation of Duties Condition | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |
User Condition | User Condition |
|
JMWE Validators
JMWE for Server/Data Center | JMWE for Cloud | Notes |
|---|---|---|
Scripted (Groovy) Validator | Build-your-own (scripted) Validator | JMWE Server uses Groovy scripting, while JMWE Cloud uses Nunjucks expressions and Jira expressions. |
Comment Required Validator | Comment Required Validator |
|
Fields Required Validator | Field Required Validator |
|
Related Issues Validator | Linked Issues Validator |
|
Related Issues Status Validator | Linked Issues Status Validator |
|
User Validator | User Validator |
|
Field has been modified Validator | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |
Field has single value Validator | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |
Previous Status Validator | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |
Parent Status Validator | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |
JMWE Post-Functions
JMWE for Server/Data Center | JMWE for Cloud | Notes |
|---|---|---|
Scripted (Groovy) operation on issue | Build-your-own (scripted) Post-function | JMWE Server uses Groovy scripting, while JMWE Cloud uses Nunjucks expressions and Jira expressions. |
Assign to last role member | Assign to last role member |
|
Assign to role member | Assign to role member |
|
Clear field(s) | Clear fields |
|
Clear field(s) of related issues | (see note) | Also handled by Clear fields in Cloud |
Comment issue | Comment issue(s) |
|
Comment related issues | (see note) | Also handled by Comment issue(s) in Cloud |
Copy issue fields | Copy issue fields |
|
Copy field value from parent issue (OBSOLETE) | (see note) | This post-function is obsolete in the JMWE for Server version 7.2.0 and later and handled by Copy issues fields when migrated to Cloud |
Copy field value from related issues (OBSOLETE) | (see note) | This post-function is obsolete in the JMWE for Server version 7.2.0 and later and handled by Copy issues fields when migrated to Cloud |
Copy field value to parent issue (OBSOLETE) | (see note) | This post-function is obsolete in the JMWE for Server version 7.2.0 and later and handled by Copy issues fields when migrated to Cloud |
Copy field value to related issues (OBSOLETE) | (see note) | This post-function is obsolete in the JMWE for Server version 7.2.0 and later and handled by Copy issues fields when migrated to Cloud |
Copy value from field to field (OBSOLETE) | (see note) | This post-function is obsolete in the JMWE for Server version 7.2.0 and later and handled by Copy issues fields when migrated to Cloud |
Create / Clone issue(s) | Create issue(s) |
|
Delete issue(s) |
| |
Display message to user | Display Message to User |
|
Email issue | Email issue |
|
Increase value of field | Increase value of field |
|
Link issues to the current issue | Link issues to current issue |
|
Sequence of Post-functions |
| |
Set issue, user or project Entity Property value | Set Entity Property value |
|
Set field value from User Property Value | Set field value from User Entity Property value |
|
Set field value | Set issue fields |
|
Set field value of related issues | (see note) | Also handled by Set issue fields in Cloud |
Add field value to parent issue | (see note) | Also handled by Set issue fields in Cloud |
Shared Action | Shared Action | Shared actions are not migrated at this time |
Transition current issue | Transition issue(s) |
|
Transition parent issue | (see note) | Also handled by Transition issue(s) in Cloud |
Transition related issues | (see note) | Also handled by Transition issue(s) in Cloud |
Unlink issues from the current issue | Unlink issues from the current issue |
|
Return to Previous Status | There is no Cloud equivalent. This post function will not be migrated. | |
Set issue security level based on current user's project role | (see note) | Originally supported by JMWE for Jira Server but currently maintained by Atlassian on Jira Cloud. |