| Table of Contents |
|---|
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 also have a selected group of users /wiki/spaces/WD/pages/209780896 with custom fields.
| Note |
|---|
Issue field has to be accessible on create screen |
...
Table below depicts the steps you can use:
...
Standard issue fields | Custom issue fields |
|---|---|
Assignee | User Picker (single user) |
Creator |
User Picker (single |
user) |
Reporter |
User Picker (single user) | |
Request participants | User Picker (multiple user) |
Approvers | User Picker (multiple |
user) |
Additionally, you can use the “Issue field - User” option to create a step for user/s mentioned inside the description of an issue. This option is available as “Description”.
...
In order for the description step to work, you must create a table with “Approval Path” header. Any users mentioned inside the table are then assigned to an approval step. Here is a template:
Approval Path |
|---|
@User1 |
@User2 |
This can be a standard field or a custom field.
In the case of a custom field, you can use a user or multi-user select field.
...
Action types
Approval
Consent - Similar to approval. More about it is on the FAQ page.
Notification
Approval / Consent action
Single user decision step. When the step is activated, the user will receive a notification with a ‘call for action’. On the Jira issue page user will see accept and reject buttons. The decision can not be changed. The only way to undo the decision is to ‘reset’ the ongoing approval path and start a new one. Every Jira page participant can start or reset the approval process.
Notification action
The user will be notified about current progress. He might be interested in knowing progress or result, but this person has no involvement in decision making. Possible use cases:
Used at the beginning of the approval process to notify shareholders about new initiatives inside a company.
Used as the last step in the approval process to notify the team leader if access to new hardware was approved.
Resolve user
There are two options that allow you to reveal the approver,
...
Once the approver is determined this step behaves the same as User Step /wiki/spaces/WD/pages/209780761.
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.