- Created by Cristina Balcázar, last modified on Dec 15, 2023
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 17 Next »
This page provides you with a quick overview of Herzum Approval administration screens and briefly introduces their purpose.
Navigate to the Manage apps Panel within your Jira instance to access the Herzum Approval Administration Screens.
The Global Configurations screen allows you to manage the following settings:
Approval General Settings
Approval Delegation → enable/disable the Approval delegation functionalities.
Approval Superusers
Super Approver → provides selected users with special privileges to approve or reject any approval
Approval Expression Superuser → User used by the app to populate the user picker custom fields case of Approval configurations based on expressions
Conditional Rule Superuser → User used by the app by default to evaluate the Conditional Rules (Not set by default). It’s mandatory to select an user in order to create a Conditional Rule.
Approval Actions
Reject Approval Action → This option allows to disable/enable the capability to reject (Enable by default)
Abstain Approval Action → This option allows to enable/disable the capability to abstain (Disable by default)
Lock Reversing Approval Actions → This option allows to lock approval actions (Disable by default)
Enable Actions on Approval Panel → This option allows to enable the rest of action when one of them has already executed.
Approval Display Options
Actions on Command-bar → This option allows to enable Approval Action on the Issue
View Approval Flow → This option allows to view approval flow
Web Panel Expanded → This option allows to maintain Approvals expanded or collapsed (Disabled by default).Enabled
View Percentage Number → This option allows to view percentage number of kept approbations (Enable by default)
Display Approvals → This option allows to default displaying only own approvals for logged user (The logged user displays all approvals by default).
Display Large Action Buttons → This option allows to display large or small buttons for selected users (No user displays large buttons by default).
Request Button Label → Customize Request Approvals button label (No label by default). If no custom label is inserted, the button default label 'Request Approvals' displays.
Customize Field Labels → Customize field labels in Approval Web Panel help (No label by default). If no custom label is inserted, the default field labels display.
Customize Action Button Labels → Customize the action button labels on issue (No label by default). If no custom label is inserted, the default button labels display.
Approval Logs via Comments
Logging Approval Events → Enable logging approval events as Jira Comments
Approval Log Text → Customize the text of the approval log.
Approval Requests and Replies by Comment → Enable notifying the approval request via a Jira comment and processing the approver response from a Jira comment.
Approval History
Enable Approval History → Enable recording the events regarding the approval flow.
Show Event Grouped by → Choose a field that will be used to group the events displayed on the Approval History tab.
Hide Events → Filter the Events that you want to display on the Approval History tab
Expand or Collapse Rows → Choose to collapse or expand, on the Approval History tab, detailed information on each event.
Apply Filter → This option allows to filter the displayed rows (None by default).
Fields Name → This option allows to choose where fields name display
Customize History Fields → This option allows to customize any field label and choose to show or hide them.
Approval Email
Email Approval Delimiter → Customize the delimiter of the approval reply @ ('@' by default)
Customize E-mail buttons → You can customize the label displayed on each button of the Approval Request Email. If a label is not set, the default label is used.
Summary
Present a table that summarizes the quantity of objects generated within the application.
Slack
Facilitates the connection of the application to a Slack channel, enabling the reception of approval notifications.
The approvals identify who can approve or reject. You must first setup Approvals on the Approvals screen in order to setup the on Approvals Mappings
The Conditional Rules Configuration Screen allows you to manage Conditional Rules that can apply to enable/disable Approvals, Minimum required Approbations/Rejections to transition an issue, and enable/disable an Email Template.
The action will execute when the condition returns true.
A Conditional Rule is a JQL expression that can be used to meet complex requirements.
The Approval Mapping screen allows you to set up your Approval Flows by Project and Issue Type and for each transition of the configured workflow.
The E-Mail Templates screen allows you to create custom email templates for Approval Request and Approval Reply emails
The Permissions screen allows you to grant to deny the permissions to Notify the Approval Requests and configure users to modify approvals for single issues and approval menu visualization
The Recipient screen allows you to disable the recipients of the emails notifying an approval Request and customize the Approval Reply notification schemes
The Audit Log administration screen allows you to monitor the administrative activities performed by any Jira Administrator on the Herzum Approval for Cloud administration screens
As a Jira Administrator, you are able to delegate the approval authority of any user to another one.
As a Jira administrator, displays the list of language packs aligned with the languages accessible within the instance
As a Jira Administrator, you are able to migrate your Herzum Approval On-premises configurations to Herzum Approval For Cloud and Herzum Approval for Cloud to Herzum Approval For Cloud.
The Troubleshooting and Support screen allows you to perform
to Check for inconsistencies of Approval Data with respect to the Jira referenced data (e.g Project, Issue Type, Users) when the Jira data changes cannot be handled by capturing a Jira event
the Recovery of inconsistencies relating to missing referenced data in Jira and in case of some unexpected errors.
Performs general tool refactoring
Any question or suggestion?
We would love to hear from you.
We will go into more detail in the following pages.
- No labels