Issue Summary

In JSM Assets, there is "User" attributes type that are linked to JIRA user or customer account. In JIRA ticket, if the customer are set as "Reporter", or are added to a custom field of "user picker type", you can access properties available in the following documentation: Automation smart values - users. However, when the same user is added to an Assets object type custom field, the properties available for the smart values are different. Currently, the properties available are:

"user": {
   "avatarUrl": <string>,
   "displayName": <string>,
   "name": <string>,
   "key": <string>,
   "emailAddress": <string>,
   "isDeleted": <boolean>
},

Steps to Reproduce

1. Add "User" attribute type in Assets Object type
2. Create an object and update the User attribute with user account.
3. Create an Assets object custom field and add to the request form or create issue screen.
4. Create an issue and update the Assets custom field with the object that have User attribute updated with the user account, and also add the account as reporter or include it in a different custom field of user picker type.
5. In automation configuration, try to access the data using the smart value and compare the results. Example:

   Reporter active status : issue.reporter.active
   Object active status : issue.Assets Object Field.User.active
   

Expected Results

Allow the automation rule to access the same properties for the user.

Actual Results

Automation for Jira is not able to access the properties for: Active status, Timezone, etc.

Workaround

As a workaround, you can use the REST API endpoint below and add it as a Send web request to your automation rule to get the user information:

• https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-get