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

« Previous Version 4 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 "approve" action approves a named approval.

"approve"

The trigger action "approve"causes an approved decision to occur for a named approval if the provided parameters are valid.

  • action (approve
  • approval (string) Name of the Approval to be approved. If not specified, default approval will be used
  • user (string) Atlassian userID of the approver

❗️ no mandatory parameter - only the "approve" action is required. If no named approval is added, the action uses the default approval in the workflow. 

"triggers":
[
	{"event": "on-change-state",
	"conditions":
	[
		{"final": "true"}
	],
	"actions":
	[
		{"action": "approve",
			"approval": "Sign-off",
			"user":"5d52a37ef0f22a0da2d6f070"}
	]}
]

(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.

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

o

  • No labels