How to update an issue when a linked asset object attribute is updated

[JEFFREY SCHNEIDER]

I have completed the reverse of this question previously, but for some reason this is escaping me.

I have an object "People" - Within the object, I have a few attributes, Name, Date, City, Key

I have a Jira custom asset field "Name" linked to the object "People". I also have 3 custom read only fields on my issue synced with an automation on transition to the corresponding attributes on the object.

I would like an automation to update the 3 read only fields on my issue when the object attribute is updated - currently the automation is triggered on the issue being transitioned, but I would much rather see the asset update the issue, rather than the issue querying the asset.

[Marc - Devoteam]

Hi @JEFFREY SCHNEIDER 

Why would you like to fill the 3 read only fields with attribute data?

You can also adjust the assets configuration on the custom field.

In the option in the config, Object attributes to display on issue view

You could specify the other attributes, like date, city.

these details will be visible in the issue.

Example:

[Raphael Lopes]

Hello @JEFFREY SCHNEIDER 

you could try something like this

Trigger "Object Updated"

[Trudy Claspill]

@Raphael Lopes 

How does this update the fields in the issues that reference the object?

[Raphael Lopes]

Hi @Trudy Claspill 

Great question — triggering "Object Updated" in Assets only starts the automation at the object level. To update fields in Jira issues that reference that object, you need to search for linked issues and apply actions to them.

Here’s how to do it:

• Use "Lookup Issues" action (Assets-aware)
  After the "Object Updated" trigger, add a "Lookup Issues" action.
• Use AQL or JQL to find issues referencing the updated object. For example:
  

  "Asset Field" = ${object.key}

Then add an action like "Edit issue" or "Comment on issue" and use smart values like ${object.Attributes} to reference updated fields.

Example use case:

• Trigger: Object in "Employees" schema is updated
• Lookup: All issues where "Employee Asset" = ${object.key}
• Action: Update a custom field or comment to show the new value

Let me know if you'd like help setting up the exact AQL/JQL based on your schema.

[JEFFREY SCHNEIDER]

@Raphael Lopes - I'm coming back to this problem after attacking a few more manageable items. I was able to build out my automation as you noted, but it doesn't look like this is possible as described, would you be able to show an example of a working automation or possibly guide me to where my mistake is? Attached is a screenshot of my work so far.

[Raphael Lopes]

Hello @JEFFREY SCHNEIDER 

How you doing?

Please, check that the scope of your automation is set to global.

[Trudy Claspill]

Hello @JEFFREY SCHNEIDER 

The problem you are encountering is that you have Looked up the work items you want to update, but that doesn't shift the "focus" of the rule to operating on those work items. When you execute the Edit Work Item action, the focus is still on the Asset Object that triggered the rule.

You need to use a Branch (For Each) after the Lookup  to shift the focus to the issues found.

There are two types of branches you could use: