Autopopulate user picker field based on expression
- Cristina Balcázar
- Paula Mantilla
All administrative functions of Herzum Approval require you to be a user with the Jira Cloud System Administrators global permission.
The Auto-populate user picker field based on expression screen allows you to specify expressions that will be used to populate a user picker All and the user picker Any that have been selected for an Approval Configuration.
Preliminary global settings
To set the Auto-populate user picker field based on an expression on your Approval Configurations, you must first enable it by activating the User picker auto-population option on the General settings
In this section
Auto-populate user picker field based on expression screen
Navigate to the Approvals administration screen and create a new Approval Configuration of the type “Single Property.”
The Approval Configuration screen displays the available properties to set up an Approval.
Here you can choose a user picker custom field that can be populated based on an expression.
On selecting a user picker All, distinct approbations will be requested to each user that will be inserted in the User Picker field.
On selecting a user picker Any, any user inserted in the User Picker custom field may provide the approval response on behalf of all users.
When selecting a user picker All or a user picker Any , you can specify expressions that identify
users that will be inserted on the user picker custom field to enable them to approve and
users that will be removed by the user picker to exclude them.
To insert an expression to populate the user picker field, click on the 
Specify the expression identifying the users to insert in the user picker custom field
The Auto-populate user picker field based on an expression screen requires an expression, respecting the expected syntax, that specifies the users to insert in the user picker field (Can Approve or Reject) and, optionally, the users to discard from the list (Excluded).
You cannot specify the users to discard (Excluded) without specifying the users to insert into the user picker field (Can Approve or Reject).
You can add allowed tags to the text areas by dragging and dropping a tag at the desired insertion point. To insert values into the property tags, simply start typing the text.
Please note that to prevent performance issues, there is a limit on the maximum number of users returned by both statements. If the “Can Approve or Reject” or “Excluded” statements return more than 100 users, only the first 100 will be considered.
Test the expression
You can test an expression to check if the list of users returned for an issue, on evaluating the Can Approve or Reject and Excluded, matches the expectations.
To test your expressions, you can specify an issue key, click on Run Test, and Review the list of users that are returned.
Property tags
The syntax that allows to specify the property's values expects a Start tag and an End tag.
The available tags are listed below:
<users>...</users>
<groups>....</groups>
<roles>....</roles>
<user-pickers>...</user-pickers>
<group-pickers>...</group-pickers>
<component-leads>...</component-leads>
Property Values
The admissible property's values depend on the selected Property.
The admissible values per property are listed below:
<users>
Username, any username
Reporter, keyword to include in the list of the issues's reporter
Assignee, keyword to include in the list of the issues's assignee
ProjectLead, keyword to include in the list of the concerned project lead
Component Leads, keyword to include in the list all the concerned Component Leads
<groups>
Group, any Jira Group name
<roles>
Project Role, any Project Role Name
<user-pickers>
User Picker custom-field, any user picker custom field identifier (Example: customfield_10125)
<group-pickers>
Group Picker custom-field, any group picker custom field identifier (Example: customfield_10188)
<component-leads>
Project Component, any Component Name. This setting maintains the Component Name and not the Component ID to allow reusing the Approval across Approval mapping for different Projects.
You can specify one or more Property's values.
The property's values must be concatenated via the ','.
Example: <users>Tom Black , Nancy Green , Jack Red , Katy White</users>
Condition Tags
The syntax that allows to specify a condition enabling a set of properties expects one of the following start-end tag:
<conditional-rule name="Conditional Rule Name">...</conditional-rule>
<conditional-rule name="Conditional Rule Name " is-false>...</conditional-rule>
The admissible names include all Conditional Rule names that you have created via the Conditional Rules administration screen.
An expression can include zero, one, or more conditions enabling one or more properties.
Example: <conditional-rule name="Priority High"><groups>Managers</groups> </conditional-rule> <conditional-rule name="Priority High" is-false><users>Tom Black</users></conditional-rule>