Issue Field - User
Issue fields can be utilized to specify steps in the approval process. For instance, you could designate the approver as either the assignee or the reporter of an issue. It is also possible to have a chosen group of users with custom fields.
Issue field has to be accessible on create screen
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”. Read more here.
Action types
Approval
Notification
Consent
Approval / Consent action
When the step is activated, a notification with a 'call for action' will be sent to the user. Users will see the 'approve' and 'reject' buttons (or Abstain button depends on set up) on Jira work item/issue. 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. Only a user with appropriate permissions can delete or archive approval.
Consent is similar to Approval. Learn more about it on the FAQ page.
Notification action
The user will be notified about the current progress. He might be interested in knowing progress or results, 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.
Requiring comment on actions
If this checkbox is selected, the approver will be required to provide a comment when approving, rejecting or abstaining an issue. This ensures that the reasons for decisions are clearly communicated, providing feedback for the assignee and keeping transparency in the approval process.
Resolve user
Two options allow you to reveal the approver,
Approval start
Step start
If the “approval start” option is selected, the approver will be revealed as soon as the approval starts, (if the approver missing from the issue field, this step will be skipped or the definition will not be created).
Step start option, however, will only reveal the approver once the path has reached to the step.
Once the approver is determined this step behaves the same as User Step.
Issue watchers notification
This feature gives an effective way to update notifications for approval paths sent to issue watchers. It grants the user the ability to prevent 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 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.