Email step
Email Step
An Email step sends the decision to an email address rather than a Jira account, so people outside your organization can take part in an approval. You either type the address in the definition, or take it from a work item field.
Choosing the approver
Email address
You type the email address here, in the definition. Every approval built from this definition goes to the same person.
Work item field
The address is read from a field on the work item, so each approval can go to someone different. Search for an email field in the Work item field box.
Use a Short text (plain text only) custom field to hold a single address. The field can be filled in after the definition has been created and even after the approval has started, as long as the value is there by the time the step reads it.
The picker lists the text fields available in your instance, so what you see depends on how Jira is set up. Standard fields such as Summary and Description appear alongside any text custom fields your admins have created, for example Department or Work category.
For several external approvers at once, pick Description, which builds the step from the addresses in the work item's description.
Picking Description builds the step from the users mentioned in the work item's description. See Work Item Fields - Description for how that works.
Resolve user(s) from field on
When the field is read, either at Approval start or at Step start. Reading at step start picks up changes made to the field while earlier steps were running.
If the field holds no address at the moment it is read, the step is skipped, or the approval is not created at all.
Once the address is resolved, the step behaves exactly like a typed one.
What the external approver sees
An external approver is someone outside your organization, with no access to Jira.
When the step activates, they receive an email from no-reply@app.approval-path.com with a link to a page showing a simplified view of the work item and the action buttons.
On a first interaction, the email invites them to set up an account. Once the account exists and the address is confirmed, they can sign in to the dashboard and see everything awaiting their decision. They can also set the account up in advance at the Approval Path registration page.
A decision is final. An external approver cannot change it, and cannot archive or delete the approval.
For a walkthrough of what this looks like from external users' side, see External User Guide for Approval Path
Action Type
Type |
What it does |
|---|---|
Approval |
The approver approves or rejects, and can abstain if that is enabled. |
Consent |
Behaves the same way as Approval. The wording differs, which matters in some organizations, but Approval Path treats them identically. |
Notification |
No decision is asked for. The person is told what is happening and the approval moves on. It suits someone who should stay informed without taking part, such as a client, a supplier or an auditor following a decision that affects them. |
Allow change of the email during the process
Shown with the Email address source only.
If the address turns out to be wrong, or the person is unavailable, this lets whoever started the approval swap it without restarting the whole thing.
Add comment on action
Turn on Add comment on each action and choose which decisions require one: Approval, Reject, or Abstain (if available).
Requiring a comment means the approver has to say why, which gives the assignee something to work with and keeps the reasoning on the record.
Watcher notifications
Notify watchers when this step is decided sends the work item's watchers an email whenever a decision is taken on this step. This can also be controlled instance-wide in the notification settings. The setting here turns it off for this step alone.
Conditions
Step condition
A step condition decides whether the step is part of the approval at all. Select a condition built from a Jira expression, and the step is included only when that condition is met.
If the condition is not met, or it errors, the step is left out of the approval.
Refer to our documentation for comprehensive details on conditions.
Label condition
A label condition does the same job using the work item's labels.
Field |
What it does |
|---|---|
With labels (required) |
The work item has to carry these labels. |
Match mode |
Any label (OR) includes the step when at least one required label is present. All labels (AND) needs every one of them. |
Without labels (excluded) |
The work item must not carry these labels. |
If the work item satisfies the condition, the step is added to the approval. If not, it is skipped.