Overview

The Approval Administration screen allows you to add, edit, manage advanced settings, delete and review your approval configurations.

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 case of Approval type Multiple Property and it explain which is the relationship between the properties you chose;
  • Roles: It shows which project roles have been selected;
  • Groups: It shows which groups have been selected;
  • User: It's which users have been selected;
  • Group Picker: It shows which group picker(single or multiple) custom field has been selected;
  • User Picker: It shows which user picker(single or multiple) custom field has been selected;
  • Reporter: If the reporter has been selected, the flag will show;
  • Assigne: If the assignee has been selected, the flag will show;

  • Project Lead: If the project lead has been selected, the flag will show;

    Info
    The ! icon appears case of the property identifying users that cannot Approve/Reject also if them satisfy the properties enabling them. This option is available only case of Approval type Multiple Property.

How to create an Approval

To require approvals in an Approval Mapping, you need first to create them.

Here's how to do it:

1. 1. Click Add Approval on the top of the Approval Administration screen
   2. Fill the fields showing up on the Add Approval Configuration screen:
      
      1. Approval Name (Required), the name identifying the Approval;
      2. Description (Optional), it's the description;
      3. Type (Mandatory)

         1. choose the option Single Property if your configuration needs a single property (E.g. Can approve users that belongs to the selected Project Roles)

         2. 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)

      
   3. Depending by the selected Type, you will display one of the following screens:
      
      

   • • Approval Configuration screen (Type: Single Property)

       Here you can fill out one property that users must satisfy to be enabled to Approve/Reject/Abstain.

You can select multiple values for a given property.

1. • • Advanced Approval Configuration screen(Type: Multiple Property)

       Here you can fill out multiple properties that users must satisfy to be enabled to Approve/Reject/Abstain. 

       The screen provides two tabs:

       • Properties identifying who can approve

       • Properties identifying who cannot approve

        Have a look at this link to see an example: How Approvals Multiple Property appears on the issue.

Properties identifying who can approve

Here you can fill out the properties that the users must satisfy to enable them to Approve/Reject /Abstain.

Additionally, you have to 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.

 The arrows on the right allows you to expand/collapse the multi-select box for a better view of the available values.

Properties identifying who cannot approve

Here you can fill out the properties that users must not meet in order to be enabled to Approve/Reject/Abstain.

 If you apply a property to approve, the same property will be unavailable into reject tab and vice-versa.

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.

 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.  

 This setting is not able to make consistent existing issue requesting already this approval. Only newly-created approvals will be consistent

Sequential Approvals

This optional setting allows you 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 and 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.

 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.