Issue field - Email
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 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 an account. An external user can setup an account beforehand by visiting registerhtml.
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.
Issue field - Email
Combing both above mentioned possibilities, issue field - Email allows you to specify external user steps that are more dynamic.
They 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.
Issue field has to be accessible on create screen
You can use the “Short text (plain text only)” custom field for adding single email address fields to your tickets.
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 / 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 firstname.lastname@example.org 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.
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.
Resolve user/users on
There are two options that allow you to reveal the approvers (value),
If the “approval start” option is selected, the value will be revealed as soon as the the approval starts (in the event of the value missing from the issue field, this step will be skipped or definition will not be created when it doesn’t contain any steps).
Step start option, however, will only reveal the value once the path has reached to the step.
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 jiraexpressions. 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.