Versions Compared
Version | Old Version 7 | New Version 8 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
When the workflow trigger event occurs, the trigger checks that any required conditions are met, and if met, the "assign"
action assigns one or more users and/or groups of users as reviewers to a named approval.
Info |
---|
One or more trigger actions can be set for a named event in the workflow. |
"assign"
Excerpt | ||||||
---|---|---|---|---|---|---|
The trigger action
Only one user and one group can be assigned in a single ❗️ Mandatory parametersuser and group parameters for assignees At least one value must be added for an assignee (using either user or group). The user parameter value must be specified unless a group is specified using the group parameter instead. † Default approvalIf no approval name is specified in the trigger action, the default approval is the approval in the state named in the trigger event condition. Ifthe state hasmultiple approvals, the default approval is the first approval listed in the state's JSON markup. Example trigger code
NotesWhen assigning a reviewer, the user parameter only accepts one userID value. The Atlassian User Identification Number (userId) is visible in the URL when viewing the User Profile. To assign multiple users as reviewers, you must use a Confluence group for the reviewers instead of a single user by using the group parameter, for example:
The trigger action |