Overview
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 action (reject) approval (string) Name of the approval to be rejected. If not specified, default approval† is used user (string) Atlassian ❗️ no mandatory parameter - only the † 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. If adding the JSON trigger using workflow builder there is no need to include the opening The Atlassian user Identification Number ( o"reject" sets a rejected decision for a named approval if the provided parameters are valid.userID of the rejector"reject" action is required. If a named "approval" is not specified, the action uses the default approval in the workflow."triggers":
[
{"event": "on-change-state",
"conditions":
[
{"final":true}
],
"actions":
[
{"action": "reject",
"approval": "Sign-off",
"user":"5d52a37ef0f22a0da2d6f070"}
]}
]
"triggers": JSON markup notation, it is added automatically by workflow builder.userId) is visible in the URL when viewing the User Profile.
Trigger actions
- change-state trigger action
- approve trigger action
- reject trigger action
- assign trigger action
- unassign trigger action
- set-message trigger action
- clean-messages trigger action
- send-email trigger action
- remove-restrictions trigger action
- publish-page trigger action
- set-expiration trigger action
- clear-expiration trigger action