Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typeflat
separatorpipe
printabletrue

Overview

When the workflow trigger event occurs the trigger checks that any required conditions are met, and if met the "unassign" action unassigns one or more users as reviewers to a named approval.

Info

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

"unassign"

    • . If not specified, the default approvalis used

    • comment - comment

    (string) Comment
    • for the assignation operation

    user (string) ❗️ 
    • user ❗️ Atlassian  userID to

    assign
    • unassign


❗️

indicates a mandatory parameter -  the assignee "user" parameter

Mandatory parameter

user parameter for the user to be unassigned

The user parameter value must be specified with the"unassign" action  action parameter.


Default approval

If no approval name is specified in the trigger action, the default approval is the approval in the state named in the trigger event condition.

If there are the state hasmultiple approvals in the state, the default approval is the first approval listed in the state's JSON markup for the state..


Example trigger code

Excerpt

The trigger action "unassign" unassigns a user to a named approval.

  • action (unassign

    • approval

    (string) Name
    • - the name of the

    Approval
    • approval to assign

Info
Code Block
"triggers":
[
	{"event": "on-change-state",
	"conditions":
	[
		{state: "Draft"}
	],
	"actions":
	[
		{"action": "unassign",
			"approval": "Triagereview",
			"user": "5d52a37ef0f22a0da2d6f070"}
	]}
]
Info

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

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

o

Example

We can use the "unassign" action to unassign remove a user as a reviewer in a state with multiple approvals.

For example, in the following Rejected state, we have two approvals, each with assigned reviewers.

Image RemovedImage Added

oAdding the The following JSON trigger, when added to the applied workflow using the workflow builder .visual editor:

Code Block
[
	{"event":"on-reject",
	"conditions":
	[
		{"state":"Rejected"}
	],
	"actions":
	[
		{"action":"unassign",
		"user":"5e6f8b4817c6640c385edb5e",
		"comment":"unassigned user"}
	]}
]
  • listens for a rejected event ("on-reject") in the Rejected state ("condition":"state":"Rejected")when

When a single rejected event occurs

,

:

  • the trigger "unassign" action removes an assigned user (identified using their Atlassian userID)

As the approval is not named in the trigger action, the assigned user is removed from the default approval, Primary.oImage Removed

image-20241009-182634.pngImage Added

The un-assignment of the reviewer is recorded in the document activity for the page.

Image RemovedImage Added
Info

In this example, a rejected event for any of the approvals in the named state causes the "unassign" action to occur. 

Trigger actions

Child pages (Children Display)page