Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The General Settings section on the Global Configuration screen allows you to enable or disable some automated tasks performed by the app (Approval Condition Settings), enable some valuable features (Automatic Workflow Transition based on Minimum Required Approbations and RejectionsApproval Delegation) and configure some application variables (Sleep time in automatic Request Approval Notification).


Approval Condition Settings

The Approval Conditions are Herzum Approval built-in Conditions allowing to avoid that an issue transitions in a specific destination workflow status until the expected approbations or rejections are meet.

This option allows you to disable/enable the functionality.

This setting expects the values ON or OFF.

By default this option is ON. It causes that the app automatically add and delete the Approval Conditions on any transition of each Workflow (Published and Draft) associated to the Projects,  Issue Types having an Approval Mapping configuration or a Single Approval configuration, when the following events occur:

  • uploading the app

  • uninstalling or installing the app

  • adding an Approval Mapping or a Single issue Approval Configuration

  • running the Approval Re-indexing

  • performing an approval Bulk-Operation

On turning OFF this option, you can expect the following:

  • disable the automatic addition and deletion of the Approval Conditions on uploading, uninstalling, installing the app or adding an Approval Mapping or a Single issue Approval Configuration or on performing an approval Bulk-Operation

  • the Workflow Cleaning will continue to work as per default so to allow the Complete Cleaning of all Approval Conditions,

  • the Approval Re-indexing will not delete or add the Approval Conditions.

Notice that in order to allow the app to work properly, you have to add the Approval conditions manually on the concerned Workflow transitions  on approbation and on rejection.

Keep in mind that you must take care to add and delete the Approval Conditions on the Published Workflows and Draft Workflows in order to avoid inconsistency and undesirable effects.

Automatic Workflow Transition

The Automatic Workflow Transition option allows you to enable the Automatic Workflow Transition based on Minimum Required Approbations and Rejections.

This option allows you to enable the functionality.

This setting expects the values ON or OFF.

By default this option is OFF. It causes that any Minimum Required Approbations and Rejections setting on each Approval Mapping or Single issue Approval configuration will be evaluated in order to establish if the concerned Transition can succeed (in other words it causes that the transition button appears).

On turning ON this option, the Minimum Required Approbations and Rejections setting on each Approval Mapping or Single issue Approval configuration will be evaluated in order to establish if the concerned Transition must run automatically.

Approval Delegation

Approval delegation is a feature that allows users with approval rights to delegate their approval authority to another user.

By default the functionality is disabled.

This option allows you to enable the functionality.

This setting expects the values ON or OFF.

Require Authentication

This settings allows to require authentication when an user performs on approval action on the issue.

When enabling this option, a select list allows to choose if approver must authenticate inserting only password or both username and password:


On enabling this option and leaving the default setting 'password',  you can expect that an user clicking any action buttons will display a screen requiring to insert his password.

Furthermore, when an user perform a Bulk Approval, on confirming, a screen requiring to authenticate

On enabling this option and selecting to require authentication via  'username/password',  you can expect that an user clicking any action buttons will display screens requiring to insert username and password.



  • No labels