[Includes] Feature Comparison

JMWE Conditions

JMWE for Data Center/Server	JWME for Cloud	Notes

JMWE for Data Center/Server	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 Data Center/Server	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	(see note)	Field Required validator exists in both Native Jira and JMWE Cloud; migrated Validators will be mapped the the Native version.
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 Data Center/Server	JMWE for Cloud	Notes

JMWE for Data Center/Server	JMWE for Cloud	Notes
Add field value to parent issue	(see note)	Handled by Set issue fields in Cloud
Assign issue	Assign issue
Assign to last role member (Deprecated)	Assign to last role member (Deprecated)	Will migrate to deprecated post function in Jira Cloud; has been replaced with Assign issue(s).
Assign to role member (Deprecated)	Assign to role member (Deprecated)	Will migrate to deprecated post function in Jira Cloud; has been replaced with Assign issue(s).
Clear field(s)	Clear fields
Clear field(s) of related issues (Deprecated)	(see note)	Also handled by Clear fields in Cloud
Comment issue	Comment issue(s)
Comment related issues (Deprecated)	(see note)	Handled by Comment issue(s) in Cloud
Copy field value from parent issue (Deprecated)	(see note)	This post-function is deprecated as of JMWE for Server version 7.2.0 and later Handled by Copy issues fields when migrated to Cloud
Copy field value from related issues (Deprecated)	(see note)	This post-function is deprecated as of JMWE for Server version 7.2.0 and later Handled by Copy issues fields when migrated to Cloud
Copy field value to parent issue (Deprecated)	(see note)	This post-function is deprecated as of JMWE for Server version 7.2.0 and later Handled by Copy issues fields when migrated to Cloud
Copy field value to related issues (Deprecated)	(see note)	This post-function is deprecated as of JMWE for Server version 7.2.0 and later Handled by Copy issues fields when migrated to Cloud
Copy issue fields	Copy issue fields
Copy value from field to field (Deprecated)	(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
Return to Previous Status	Return to Previous Status
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.
	Sequence of Post-functions
Set field value (Deprecated)	Set issue fields	Handled by Set issue fields in Cloud
Set field value of related issues (Deprecated)	(see note)	Handled by Set issue fields in Cloud
Set field value from User Property Value	Set field value from User Entity Property value
Set issue fields	Set issue fields
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.
Set issue, user or project Entity Property value	Set Entity Property value
Shared Action	Shared Action	Shared actions are not migrated at this time
Transition current issue	Transition issue(s)
Transition parent issue (Deprecated)	(see note)	Also handled by Transition issue(s) in Cloud
Transition related issues (Deprecated)	(see note)	Also handled by Transition issue(s) in Cloud
Unlink issues from the current issue	Unlink issues from the current issue