| Table of Contents |
|---|
Issue fields may can be used utilized to define specify steps in the approval process. For exampleinstance, you may choose could designate the approver to be as either the assignee or the reporter of an issue. You can It is also possible to have a selected /wiki/spaces/WD/pages/209780896 chosen group of users with custom fields.
| Note |
|---|
Issue field has to be accessible on create screen |
...
Table The 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) |
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.
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.Read more here.
...
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’'call for action' will be sent to the user. On the Jira issue page user , users will see the accept and reject buttons. The decision can not be changed. The only way to undo the decision is to ‘reset’ the ongoing approval path It's important to note that once a decision is made, it remains final, and the only way to roll it back is to delete the current approval and start a new one. Every Jira page participant can start or reset the approval processOnly a user with appropriate permissions can delete or archive approval.
Notification action
The user will be notified about the current progress. He might be interested in knowing progress or resultresults, 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 Two options that allow you to reveal the approver,
...
If the “approval start” option is selected, the approver will be revealed as soon as the the approval starts, (in the event of if the approver missing from the issue field, this step will be skipped or the definition will not be created).
...
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.