Info | ||
---|---|---|
| ||
You must have the Jira System Administrators global permission before you can carry out the instructions on this page. |
Overview
The Approval Administration screen looks like as follows:
The Approval Administration screen screen allows you to add, edit, manage advanced settings, delete and review your approval configurations.Furthermore, when
The Approval Administration screen looks like as follows:
When moving the mouse upon an approval name, a window, explicating the applied settings, shows up.
In details:
- Approval Name: It identifies the approval and once it's created it cannot be renamed;
- Operator: It's populated only if you choice multiple property case of Approval type Multiple Property and it explain which is the relationship between all the properties you chose;
- Roles: It shows which project roles has have been selected for that approval;
- Groups: It shows one or more groups that has which groups have been selected;
- User: It's the list of the single users that has been chosenwhich users have been selected;
- Group Picker: If one or more group picker custom fields has been created, it will show which one It shows which group picker(single or multiple) custom field has been selected into the property;
- User Picker: Just like the group picker custom fields but for single users and not a groupIt shows which user picker(single or multiple) custom field has been selected;
- Reporter: If the reporter is selected into the approval the has been selected, the flag will show;
- Assigne: If the assignee is selected into the approval the has been selected, the flag will show;
- Project Lead: If the project lead is selected into the approval the has been selected, the flag will show;
How to create an Approval
To require approvals in an Approval Mapping, you need to create it.
Here's how to do it:
- Click Add Approval on the top of the Approval Administration screen
- Fill the fields showing up on the Add Approval Configuration screen
:- Approval Name (Required), the name identifying the Approval;
- Description (Optional), it's the description;
- Type (Mandatory)
choose the option Single Property if your configuration needs a single property (E.g. Can approve users that belongs to the selected Project Roles)
choose the option Multiple Property if your configuration needs multiple properties at the same time (Project Roles, Groups, Users, Group Picker Field, User Picker Field, Issue Reporter, Assignee and Project lead)
- Depending by the selected Type, you will display one of the following screens:
Approval Configuration screen (Type: Single Property)
Fill out the property that users must satisfy to enable them to Approve/Reject/Abstain the approval request.
You can select multiple value for a given property.
Advanced Approval Configuration screen(Type: Multiple Property)
Using a multiple property will lead into two different tabs
Properties identifying who can approve:
Fill out the properties that users must satisfy to enable them to Approve/Reject /Abstain the approval request
Info The arrows on the right allows you to expand/collapse the multi-select box for a better view of the available values.
Specify if the users enabled to Approve/Reject/Abstain must satisfy all the selected properties or at least one of them
E.g. If you have selected a project role, a group and the reporter, flagging the first option it means that any user that belongs to anyone of those properties selected may approve/reject.If, instead, you flag the second option the approver can be only an user (or more) that belong at the same time to all the properties selected.
Info To more details see this example: MultiplePropertySettings
Properties identifying who cannot approve:
Info Warning: If you apply a property to approve, the same property will be unavailable into reject tab and viceversa. For more details check this example: Multiple Property With Exclusions
Manage Approval Advanced Settings
Click the cog symbol on the right of the screen and select one of the following advanced settings:
Condition Approval Disabling
This optional setting allows to enable the Approval only if the associated conditional rule, evaluated on the specific issue, returns true.
If None condition is selected the Approval will be enabled always.
Info |
---|
This setting is not able to make consistent existing issue requesting already this approval. Only newly-created approvals will be consistent |
Displaying Options
This optional setting allows to choose the information that you want to display in the Approval Column of the Approval History tab.
By default, the Approval Column displays the the Approval Name and Approval Detail:
Sequential Approval Disabling
This optional setting allows to disable the sequential approval for the specific Approval so that if an Approval Mapping requires the Sequential Approval, this specific approval can be approved in any order.
Info |
---|
This setting is not able to make consistent existing issue requesting already this approval. Only newly-created approvals will be consistent |
Setup Sequential User Picker
This optional setting allows to establish the approval sequence on the selected users case of an Approval based an user-picker custom field.
This setting can be managed on the Approvals associated to an User Picker Field All property.
This setting is hidden case of Approvals not associated to an User Picker Field All property.
If the selected User Picker Field includes any user not included in the Sequential Users Picker list, the user will be sequence independent.
Info |
---|
This setting is not able to make consistent existing issue requesting already this approval. Only newly-created approvals will be consistent |
Editing an Approval
You are able to update an existing approval.
Most of the filled fields can be updated, exception made for the Approval Name and the Category.
The applied changes will apply contextually on any issue expecting the modified Approval.
Deleting an Approval
When deleting an approval not yet associated to any Approval Mapping or Single Issue Approval Configuration, the application doesn't ask to confirm.
If in any configuration requiring the Approval exists, the application asks to confirm.
The applied changes will apply contextually on any issue expecting the Approval.