Page Comparison

The trigger action "reject" causes a rejected decision to occur for a named approval if the provided parameters are valid.

• action (reject) 
• approval (string) Name of the approval to be rejected. If not specified, default approval^† will be used
• user (string) Atlassian userID of the rejector

^{❗️ no mandatory parameter - only the"reject" action is required. If a named approval is not specified, the action uses the default approval in the workflow.}

^{† 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.}

"triggers":
[
	{"event": "on-change-state",
	"conditions":
	[
		{"final": "true"}
	],
	"actions":
	[
		{"action": "reject",
			"approval": "Sign-off",
			"user":"5d52a37ef0f22a0da2d6f070"}
	]}
]

 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.

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

o