In this section
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Approval allows users to automatically transition an Issue that meets the specified conditions by either approving or rejecting it.
Start by accessing the Project Settings module. Here, you can set up approval processes for different requests.
Creating Approval involves several steps to define the Approval criteria and behavior.
Access the Approval For Jira application in project
Navigate to the sidebar of your Jira instance.
Locate the "Apps" group.
Within the "Apps" group, find and click on the "Approval for Jira" app module.
Click on the "Add Approval" button. This will open the Approval Configuration interface where you can set up the criteria and process for your approval.
Steps to Create an Approval:
🎯 Step 1 - Naming & Select the Approver(s)
Specify a descriptive Approval Name: You need to specify the name indicating the purpose of the Approval (e.g., "Review Design", "Code Review").
Assign appropriate Approvers: Determine who should have the authority to approve or reject Approval. You can assign individuals, groups, or departments based on their roles and expertise.
| Note |
|---|
Note: The Approval namemust be unique and cannot be duplicated. |
🎯 Step 2 - Select Issue Type and Source Status
Select Issue Type: Select the appropriate Issue Type (e.g., Bug, Task, Story).
Select Source Status: Choose the relevant Source Status (e.g., Open, In Progress, Resolved) to focus on issues at specific stages of the workflow.
Additional Filter(Optional): Utilize the Additional Filters option to refine your approval criteria further. This option allow selecting Custom Fieldwith equivalent value.
Skip transitions (Optional): Check this box if you want tobypass the transition step.To prevent an automatic transition and require manual intervention afterApproval process.
| Note |
|---|
Note: Current Limitations of Additional Filters
|
🎯 Step 3 - Select Approval Transition
Select Destination Status: Choose the desired Status that the issue will transition to once it's Approved (e.g., "Resolved," "Closed," "In Review").
| Note |
|---|
Note: Approval for Jira allows you can specify a specific destination status for approved or rejected issues. |
🎯 Step 4 - Select Decline Transition
Select Destination Status: Choose the desired Status that the issue will be transitioned to if it's Declined (e.g., "Reopened," "Rejected," "Closed").
🎯 Step 5 - Configure Approval Condition(s)
All Approved: Select this option if you require Approval from all assigned Approvers before the issue can transition.
Minimum Approval: Specify the minimum number of Approvers needed for the issue to transition. This allows for scenarios where a majority vote is sufficient.
🎯 Step 6 - Add OLA (Optional)
Time Target: Set the OLA time for approval to create a clear timeframe for making both approval and rejection decisions.
| Note |
|---|
Note:
|
🎯 Step 7 - Review and Confirm
Verify Settings: Carefully examine the summary to ensure that all settings are correct and aligned with your intended approval process.
Make Adjustments: If necessary, modify any settings that are incorrect or do not meet your requirements.
Use Case
Approval are essential mechanisms for ensuring that decisions are made consistently, efficiently, and with appropriate authorization. They are particularly valuable in scenarios where accuracy, compliance, or resource allocation are critical.
To learn more about specific use cases and best practices for implementing Approval, please visit our dedicated page:
Click here: Use Cases for Approval.
This page is here to offer you detailed insights on leveraging approvals to streamline your business operations.
Strict Approval Process
These settings are designed to enhance the stringency of the Approval setup and mitigate potential risks effectively.
Click here: Strict Approval Process.
This page will provide the necessary setup for making the Approval setup more strict.