Support "user" smart values for custom fields with "User Picker" search template (v 2.5)

SINCE VERSION 2.5
User Profiles for Jira gives you the possibility to use a custom field of type "User Profile Field" as smart value within Automation for Jira. This is applicable for custom fields that use the "User Picker & Group Searcher" as search templates. This allows the use of the smart value where Automation for Jira expects an actual user and not just it's String representation.

There is a distinction in the representation of the user from custom fields of Jira's standard type “User Picker (single user)”. When using a custom field of type "User Profile Field", the value {{issue.CustomFieldName}} will resolve to the complete JSON representation of the user. On the other hand, for custom fields of type “User Picker (single user)”, {{issue.CustomFieldName}} will resolve to only the user's name. It is important to consider this distinction when formulating Jira automation rules as it can impact the outcomes. Please refer to the following code snippet - demonstrating how to update the approvers of an issue using advanced field editing - for a clearer understanding of the dissimilarity.

{"update": {
  "Approvers": [
 {"add": {"name":"{{issue.JiraUserPickerField}}"} //custom field created through Jira},
 {"add": {"name":"{{issue.UserProfileField.name}}"} //custom field created through our application}
    ]}}