...
Issue fields may be used to define steps in the approval process. For example, you may choose the approver to be the assignee or the reporter of an user with the email address from the selected string field from the issue. You can use custom fields that are populated with your information.
...
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 set up an account. An external user can setup set up an account beforehand by visiting https://app.approval-path.com/register.html. Approval Path registration.
Once an account is setup set up and the email address is confirmed, they can log in to the dashboard and see a list of awaiting approvals.
Issue field - Email
Combing Combining both above mentioned possibilities, the issue field - Email allows you to specify external user steps that are more dynamic.
They The field can be populated after the definition is created and started
You can select a list of external approvers (multiple external approvers)
You can Resolve user/s on approval start or step start. More here.
...
| Note |
|---|
Issue field has to be accessible on create screen |
...
For multiple external approvers, you can use the description of an issue. This option is available as “Description” under the “Issue field - Email” drop-down menu.
In order for the description step to work, you must create a table with “Approval Path” header. Any email addresses inside the table are then assigned to an approval step. Here is a template:
...
Approval Path
...
...
...
Action types
Approval
Consent - Similar to approval. More about it is on the FAQ page.
Notification
Approval / Consent action
Single When the single-user decision step . When the step is activated, then the an external user will receive an email notification with a ‘call for action’. A message will come 'call for action' from the no-reply@mail.approval-path.com email address. The email will contain a link to the a page with simplified Confluence page content and action buttons. The Please note that once made, the decision cannot be changed. An , and an external user cannot reset delete or archive the approval.
Notification action
The user will be notified about the current progress. They might be interested in knowing progress or resultresults, but this person has no involvement in decision-making.
Resolve user/users on
There are two Two options that allow you to reveal the approvers (value),:
Approval start
Step start
If the “approval startApproval Start” option is selected, the value will be revealed as soon as the the approval starts (in the event of if the value missing from the issue field, this step will be skipped or the definition will not be created when it doesn’t contain any steps).
The "Step startStart" option , however, will only reveal display the value once the path has reached to the step. After the approver is determined, this step functions similarly to an Email Step.
Issue watchers notification
This functionality empowers to manage the feature gives an effective way to update notifications for approval paths sent to issue watchers. It provides grants the user the ability to prevent the reception of unnecessary notifications, enhancing overall communication efficiency.
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/ Jira expression. 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.