Webhook step

Open

With the webhook step, you can introduce automation to your approval process management. You can place the webhook step at any place in the approval path. With the automation plugin, you can alter the page if the approval path reaches the webhook step. Example automation actions upon webhook:

• Release a version

• Update an issue

• Create issue link

With the webhook step at the beginning, you can prepare the page for the approval process. If placed at the end of the process, you could for example transition the page to the next phase. A webhook involves an HTTP call where you need to specify a URL and method (GET/PUT/POST/DELETE). Additionally, it's optional to specify an HTTP body and headers.

Dynamics Values

Inside the URL, headers and body you can use dynamic values:
You have to put names inside ${…}

Action Type

In the case of Approval and Consent types, we expect the HTTP endpoint to return an HTTP code between 200 and 299 inclusive. This will result in the “Approved” step. In case of other response codes or problems with the connection step will be marked as “Rejected”.

Notification type will always mark a step as “Approved”, no matter what kind of response we will receive or if there will be any problem with the connection.

Issue watchers notification

This feature gives an effective way to update notifications for approval paths sent to issue watchers. It grants the user the ability to prevent unnecessary notifications, enhancing overall communication efficiency.

Create step condition

To implement a specific step into the approval process based on a predefined condition in a Jira expression, use the 'Create Step Condition' feature. Once a condition from Jira Expressions is selected, the step becomes part of the approval workflow only when the condition is met. If the condition is not fulfilled or encounters an error, the step is excluded from the approval process. Refer to our documentation for comprehensive details on conditions.