What is rejection step?
A mechanism (essentially a webhook step) triggered upon rejection that can be integrated with Jira automation rules to automate actions in response to an approval rejection, such as automatically updating the issue status.
Users may set rejection step while creating approval definitions.
Should rejection steps be set?
Rejection step is an optional step and not required to be set, it will however enable automation for when an approval is rejected.
How to set rejection step?
Depending on your need and Jira access, you can navigate to Global or Project settings of Approval Path
Global setting of Approval Path (apps dropdown menu) - requires Global admin permissions
Project settings of Approval Path (side-bar menu) - requires project admin permissions
Select the “Definitions” tab
Either create a new approval definition or edit an existing one
Ensure an approval step is set before adding a rejection step
Click on the “Add rejection step” button
The screen that follows will show
This webhook step can now be configured to respond to any custom call backs (including Jira automation rules)
If you wish to enable automation, here is a step by step guide Jira Automation
To add an automation rule, that will change the status of an issue to “done”, when an approval path is finished, you need to:
1.Go to Project Settings → Automation → Create rule
2.Add Trigger - Incoming Webhook
3.Save the webhook URL. It will be needed in the further step.
4.Add component - New Action
5. Select Transition issue. As Destination status select Done.
6. As an actor, select a user that has permission to close an issue.
7.Add a webhook step to an approval path definition. In our example, a webhook step will be the last step. In the Request field paste the webhook URL.