Herzum Approval Documentation 4.X
Page tree
Skip to end of metadata
Go to start of metadata
Customer Requirement

How to implement an approval by component lead?

In particular I need to receive distinct approvals from all Component Leads depending by the Issue's selected Components.

How to implement the customer scenario

Step 1 - Create the User picker custom field (multiple users) that will be filled with the Component Leads depending by the Issue's selected Components

If you want to use an existing custom field, go to the next step.

 Create the Approval Configuration

You can review instruction to create a custom field on the related Atlassian documentation.

You do not need to add this custom field to any Screen and you do not need to specify any Context.

Step 2 - Create the Approval configuration to identify approvers

You can update an existing Approval Single Property or create a new one.

 Create the Approval Configuration
  1. Navigate Add-ons → HERZUM APPROVAL →Approvals.
  2. Click the Add Approval button.
  3. Fill the Add Approval Configuration form

  4. Fill the User Picker Field All by selecting the User Picker custom field

  5. Click
  6. Specify the expression to populate the custom field

    (info) This configuration allows to consider All available Project Components.
    (info) You are able to specify the Components to consider using the tags <component-leads></component-leads>.
    E.g. <component-leads> Billing Services, Data Center Services, Webstore Purchasing Services</component-leads>
  7. You are able test the expression on an issue in order to check its correctness
  8. Save the Expression
  9. Save the Approval configuration
 Update the Approval Configuration

You can update an existing Approval Single Property by specifying the expression to populate the user picker custom field.

  1. Click
  2. Specify the expression to populate the custom field
  3. Save the Expression
  4. Save the Approval configuration

(warning) You can expect that this updated setting is active on any issue that have not already moved in the status requiring this approval.

Case of issue that are already waiting this approval, the updated setting becomes active on loading the issue or running an Approval Re-indexing.

Step 3 - Create the Approval Mapping configuration 

You can update an existing Approval Mapping or create a new one.

Screenshot of the Approval Mapping

How it works

Assuming to have the following Component Leads for a Project.

When the issue moves in the Status configured to request the Approvals, the user picker custom field is filled with the Component Leads of the Component that have been selected on the issue.

It causes that, for each user in the picker field, a distinct approval shows up in the Approvals panel.

In this section

Related Documentation

Here you can find some links to our customer documentation relating to the configuration screens  addressed in this page:

Other examples for Auto populate user picker field based on expression configurations

Still need help?

We would love to help.

This page contains macros or features from a plugin which requires a valid license.

You will need to contact your administrator.

Submit a support request

  • No labels