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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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 (or a valid user type workflow parameter)
  • user (string) ❗️ Atlassian userID from the assignee (and/or a valid user type workflow parameter)
  • group (string) Atlassian groupID or groupName to assign (and/or a valid group type workflow parameter)

❗️ indicates a mandatory parameter -  the assignee user parameter value must be specified with at least one user and/or group 

"triggers:"
[
	{"event": "on-change-state",
	"conditions":
	[
		{"final": "true"}
	],
	"actions":
	[
		{"action": "assign",
			"approval": "Triagereview",
			"user": "5d52a37ef0f22a0da2d6f070"
			"group": "qa_reviewers"}
	]}
]

(info) 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 include "group":"qa_reviewers". The group parameter can use both the groupID and the Confluence groupName.

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

Either a user (or list of users) or a group (or list of groups) must be specified at least.

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

  • No labels