...
| Table of Contents |
|---|
...
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 reached the webhook step. Example automation actions upon webhook:
...
Inside URL, headers and body you can use dynamic values:
You have to put names inside ${…}
Name | Description |
|---|---|
| Project id |
| Issue id |
| Approval name |
| Approval id |
Action Type
In the case of Approval and Consent types, we expect the HTTP endpoint to return HTTP code between 200 and 299 inclusive. This will result in the “Approved” step. In case of other response code or problem with 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 functionality empowers to manage the update notifications for approval paths sent to issue watchers. It provides the ability to prevent the reception of unnecessary notifications.
Create step condition
This feature allows the inclusion of a specific step in the approval process if it aligns with a condition defined in a https://developer.atlassian.com/cloud/jira/platform/jira-expressions/. Once selected, the step will only be added to the approval workflow solely when the condition is fulfilled. Should the condition not be met or encounter an error, the step will not be part of the approval process. Find more regarding conditions in our documentation.