...
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
The option is for users to toggle approval path update notifications on or off, allowing them to manage their preferences and avoid receiving unnecessary notifications.
Create step condition
A "Create step condition" for a user involves the option to include a specific step in an approval process only if a predefined condition is satisfied. When activated, this feature ensures that the step is added to the approval workflow solely when the specified condition is met.