This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

assign trigger action

Overview

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

When the workflow trigger event occurs the trigger will check 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.

"assign"

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

  • action (assign

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

  • comment (string) Comment for the assignation operation

  • assigner (string) Atlassian  userID from the assigner

  • user (string) ❗️ Atlassian userID for the assignee

  • group (string) Atlassian groupID or groupName for assignees

❗️ Mandatory parameters

  • the assignee "user" parameter value must be specified with at least one user unless you instead specify at least one group using the "group" 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": [ {"final":true} ], "actions": [ {"action": "assign", "approval": "Triagereview", "user": "5d52a37ef0f22a0da2d6f070" "group": "qa_reviewers"} ]} ]

 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.

To assign members of a Confluence group as reviewers instead of a single user you can use the "group" parameter, for example "group":"qa_reviewers" where "qa_reviewers" is a Confluence group name.

The "group" parameter can use both the groupID and the Confluence groupName.

At least one assignee must be specified - either a user or a group or one of each

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

o

You can only assign one user and/or one group in a single "assign" action. You cannot add multiple values for the "user" or "group".

The trigger action "unassign" will remove a user or members of a Confluence group from a named approval.

Trigger actions

Related Pages