Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


false
Info
icon

You must have the Jira System Administrators global permission before you can carry out the instructions on this page.


false
Info
icon

Before you can setup the Project and the Issue Types that involve approval steps, you must set up the users who are involved in approval processes.

The The Approval Administration screen  screen allows to assign Approvals to Passign Approvals to Project Roles, Groups, Users, Group Picker Field, User Picker Field, Issue Reporter, Assignee Assignee and Project  Project lead.

You can reuse an Approvals can reuse an Approvals across different Approval  Approval Mappings. 

You can define complex configurations configurations concatenating multiple  multiple properties.

Furthermore, you can can exclude users  users (E.g. Require approval of users in the group Quality Assurance with the exclusion of the reporter).


Overview

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

The The Approval Administration screen  screen looks like as follows:

Image Modified


When moving the mouse upon an approval name, a window, explicating the applied settings, shows up.

Image Modified

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 
    • type Multiple Property

  •  and
    •  and it explains 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;

  • The 
    • The !

  •  icon
    •  icon appears case of the property identifying users that cannot Approve/Reject also if they 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. Click Add Approval on the top of the Approval Administration

  1.  screen
    1.  screen

    2. Fill the fields showing up on

  2. the 
    1. the Add Approval Configuration

  3.  screen
    1.  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

  4.  Multiple Property 
        1.  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)

      Image Modified
    1. Depending by the selected Type, you will display one of the following screens:

      • Approval Configuration screen (Type: Single Property)

        Here you can fill

  5. out 
      • out one

  6.  property
      •  property that users must satisfy to be enabled to Approve/Reject/Abstain.

Image Modified

You can select multiple values for a given property.

Image Modified
      • 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

        (info) 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

Image Modified

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.

Image Modified

(info) 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 must not meet in order to be enabled to Approve/Reject/Abstain.

Image Modified

(info) If  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:

Image Modified

Condition Approval Disabling

This optional setting allows to enable the Approval only if the associated conditional rule, evaluated on the specific issue, returns true. 

Image Modified

(info) If None condition is selected the Approval will be enabled always.

(info) This  This setting is not able to make consistent existing issue requesting already this approval. Only  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.

Image Modified

(info) By default, the Approval Column displays the the Approval Name and Approval Detail:
Image Modified

Sequential Approval Disabling

This optional setting allows to disable the sequential 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.  

Image Modified

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

Sequential Approvals

This optional setting allows you to establish the approval sequence on sequence on the selected users case of an Approval based an user-picker custom field.

Image Modified

(info) This setting can be managed on the Approvals associated to an User Picker Field All property and is and is hidden case of Approvals not associated to an User Picker Field All property.

(info) If the selected User Picker Field includes any user not included in the Sequential the Sequential Users Picker list, the user will be sequence independent.

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

Editing an Approval

You are able to update an existing approval, including its Name and the applied configuration.

All the filled fields can be updated, exception made for the Categoryfor 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 any Approval Mapping or  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.

Image Modified

The applied changes will  apply contextually on any issue expecting the Approval.