Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

You can specify external users, outside your organization (without access to Jira) to participate in the approval process. We will send an email with an invitation to an external user in case of first interaction. They will have to setup an account. Once an account is setup and the email address is confirmed, they can log in to the dashboard and see a list of awaiting approvals. An external user can setup an account beforehand by visiting https://app.approval-path.com/register.html. Page with accept and reject buttons will be displayed along with simplified page content.

Action types

Approval / Consent action

Single user decision step. When the step is activated, then the external user will receive an email notification with a ‘call for action’. A message will come from the no-reply@mail.approval-path.com email address. The email will contain a link to the page with simplified Confluence page content and action buttons. The decision cannot be changed. An external user cannot reset approval.

Notification action

The user will be notified about current progress. They might be interested in knowing progress or result, but this person has no involvement in decision making.

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.

  • No labels