How does it work

To run an approval process, you need to define it first.

Such a definition can be specified by an admin on a global, or project-specific level (a global admin will have access to the app on a global level).

Every definition may consist of an unlimited number of steps.

For more detailed information on the app, check our

Documentation

️Available step types are:

  •  User step

User step

  •  Group step

Choose a group and voting criteria (number of votes required to pass/reject)

  •  Email step

Email step → add users outside your Jira (i.e., a customer)

  •  Issue Field - User

Choose a user from the issue field (i.e., assignee, reporter)

  •  Issue Field - Group

Choose a group from the issue field

  •  Issue Field - Email

Specify dynamic external user steps (from issue field)

  •  Automation step

Apply a default automation process, i.e., change the issue status, the assigned user, or add a comment

  •  Webhook Issue

Create automation to send or receive requests, including a rejection step triggered by approval denial

To every definition or even every step, a condition (created using Jira expressions) can be applied. Steps can be run sequentially (by default) or you can create a parallel group and put some (or all) steps simultaneously. For each step, you can choose what action is required: 'approval', 'consent', or 'notification' (to only notify someone about the current progress).

Users can approve/consent, reject, or abstain with or without an additional comment. And, if someone is absent, a delegation can be created to ask another person to take action on behalf of the missing one.

Definitions serve as a template for approval and can be run multiple times. Several approvals can be launched simultaneously for a single issue (each one can be customized). You can set automatic reminders, send manual reminders, and watch the approval process live or see its report in the history/comment tab.

Integrates with Jira Permission Schemes, so if you need to grant or revoke specific permissions, there’s room for customization.

How it’s different from other apps? Check our comparison here .

Approval Path definition example

When to use the App

Well, it depends on you - whenever you need to receive feedback or permission. From our personal experience, there are the following use cases::

Budget approval

Customer feedback

Code review

Purchase process

Design approval

Product development

Business trip planning and approvals

Offer proposals (and discounts)

Target Audience

Ideal for enterprises, companies undergoing audits, and medium to large businesses requiring strong governance and compliance, such as automotive, transportation services, military, government, and banking sectors.