Page Comparison

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

• action (unassign) 

• approval (string) Name of the Approval to assign. If not specified, default approval^† will be

  used†

  used

• comment (string)

   Comment

   Comment for the assignation operation

• ID

  user (string) ❗️ Atlassian 

  user

  userID to assign

❗️ indicates a mandatory parameter -  the assignee "user" parameter value must be specified with the "unassign" action parameter.

^† _{If no approval is specified in the trigger action, the default approval is the approval in the state named in the trigger event condition. If there are multiple approvals in the state, the default approval is the first approval listed in the JSON markup for the state.}

"triggers":"
[
	{"event": "on-change-state",
	"conditions":
	[
		{state: "Draft"}
	],
	"actions":
	[
		{"action": "unassign",
			"approval": "Triagereview",
			"user": "5d52a37ef0f22a0da2d6f070"}
	]}
]

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

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

o

Image Removed

Image Added

[
	{"event":"on-reject",
	"conditions":
	[
		{"state":"Rejected"}
	],
	"actions":
	[
		{"action":"unassign",
		"user":"5e6f8b4817c6640c385edb5e",
		"comment":"unassigned user"}
	]}
]

In this example, a rejected event for any of the approvals in the named state will cause the "unassign" action to occur.