reject trigger action

Overview

You can use this action in a workflow trigger to reject a workflow approval. This action completes the approval (as a rejected approval) even if there are pending assigned reviewer decisions or a reviewer approval decision.

When the workflow trigger event occurs, the trigger checks that any required conditions are met, and if met, the "reject" action rejects a named approval.

One or more trigger actions can be set for a named event in the workflow.

`"reject"`

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

action (reject)
- approval Name of the approval to be rejected. If not specified, default approval^† is used
- user ❗️ Atlassian userID of the rejector

❗️ Mandatory parameter

user

The trigger action must define a value for the user parameter for the reject action to take place.

†Default approval

If the trigger action does not specify a named approval, the action uses the default approval in the workflow.

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.

Example trigger code

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

If adding the JSON trigger using workflow builder visual editor, there is no need to include the opening "triggers": JSON markup notation; it is added automatically by workflow builder.

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

o