Automation smart values - Assets

[Javid Huseynli]

Hi,

I have a JSM Cloud project with the following setup:

Assets object schema — Squads and Divisions:

• Object xx-123: managers = user1
• Object xx-456: managers = user2
• The managers attribute type is User

Issue setup:

• Custom Assets field Squads and Divisions (customfield_14135) — links to one of the above objects

Goal: When an issue transitions status → read the Managers User attribute from the linked Assets object in customfield_14135 → set that user as Approvers on the issue.

What I tried in Edit Issue action (Approvers field):

{{issue.customfield_14135.managers}} 
{{issue.customfield_14135[0].managers}}
{{issue.customfield_14135.object.managers}}

Added a debug comment:

{{issue.customfield_14135}}

All return empty. The rule runs successfully with no errors, but Approvers stays empty and the debug comment is blank.

What is the correct way to read a User-type attribute from an Assets object linked via a custom Assets field, and use it to populate the Approvers field in an automation rule?

Thanks in advance!

[Timothy Brown · Accepted solution]

If the field you're referencing points to an asset record, I found that you need to use the following syntax:

objectType= "Users" AND "Name"="{{issue.customfield_XXXXX.mangers}}"

This approach tends to work well when dealing with Object type fields in Assets.

[Marc -Devoteam- · Accepted solution]

Hi @Javid Huseynli 

Welcome to the community.

See this KB article; how-to-auto-populate-approvers-from-asset-objects-attributes-using-automation-in-assets this should help you out I think

[ben_snyder · Accepted solution]

Hi @Javid Huseynli

Ben here from Appfire. 

In case you needed another approach, I wanted to add some more resources.

Since working with Assets object attributes in Jira Service Management Cloud can be a bit tricky, especially when you're trying to pull specific data using native automation smart values. While Jira's built-in automation is powerful, it often faces limitations when trying to traverse the relationship between an issue and the detailed attributes of an object selected in an Assets custom field. Generally, the most common native approach involves using the `issue.Custom Field Name.Attribute Name` syntax, but this doesn't always reliably fetch nested data or handle complex object schemas as expected. If you find that the smart values aren't returning the values you need, it's often because the automation engine hasn't fully indexed those specific attribute paths for the trigger or action you are using.

To help bridge this gap, Jira Miscellaneous Workflow Extensions (JMWE) offers a more robust way to interact with Assets data through its scripting capabilities. By using Nunjucks scripts, you can leverage the `insightFieldValue` filter to precisely target and retrieve any attribute from an Assets object. This is particularly useful if you need to use those attributes to update other issue fields, set transitions, or perform calculations that native smart values might struggle with. Instead of relying on the standard automation syntax, JMWE allows you to access the full object data model directly within your workflow transitions or scheduled actions, ensuring that you can pull the exact piece of information—like a serial number, owner, or location—and use it dynamically across your project.

I hope this helps and welcome to the community!

Ben Snyder