Page Comparison

The trigger action "assign" will  will assign a user to a named approval.

• action (assign) 
• approval (string) Name of the Approval to assign. If not specified, default approval will be used
• comment (string) Comment for the assignation operation
• assigner (string) Atlassian  userIDfrom  from the assigner (or a valid user type workflow parameter)
• user (string) ❗️ Atlassian userID from the assignee (and/or a valid user type workflow parameter)
• group (string) Atlassian groupID groupID or groupName to assign (and/or a valid group type workflow parameter)

^{❗️ indicates a mandatory parameter -  the assignee "userparameter " parameter value must be specified with at least one user and/ or instead specify at least one group} 

"triggers:"
[
	{"event": "on-change-state",
	"conditions":
	[
		{"final": "true"}
	],
	"actions":
	[
		{"action": "assign",
			"approval": "Triagereview",
			"user": "5d52a37ef0f22a0da2d6f070"
			"group": "qa_reviewers"}
	]}
]

 if  If adding the JSON trigger using workflow builder there is no need to include the opening "triggers:" JSON markup notation, since It will be added by workflow builder.

To assign members of a Confluence group as reviewers instead of a single user include "group":"qa_reviewers". The "groupparameter " parameter can use both the groupIDand  and the Confluence groupName.

The trigger action "unassign" will  will remove a user or members of a Confluence group from a named approval.

Either At least one assignee must be specified - either a user (or list of users) or a group ( or list of groups) must be specified at least.one of each

The Atlassian user Identification Number (userId) is visible in the URL when viewing the User Profile

o

 You can only assign one user and/or one group in a single "assign" action. You cannot add multiple values for the"user"or "group".