nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Updating Asset custom field with reference from lookupObject

Robert Wen_Cprime_

I'm coming at my wit's end here.

I have an automation set up to look at one Asset custom field (Impacted Configuration Items), and collect in a lookup Action.

From that action, I want to view the references it has and update a second Asset custom field (Affected Service Offering(s)).

Screenshot 2023-06-13 at 11.15.21 AM.png

I set up a Log Action to verify it's picking up the correct objects.

Screenshot 2023-06-13 at 11.15.35 AM.png

But it fails, giving me the following error:

Screenshot 2023-06-13 at 11.26.39 AM.png

Where am I going wrong?

Accepted answers

Rick Westbrock

I ended up finding the answer (for my specific use case anyway) in another thread here: https://community.atlassian.com/t5/Jira-Service-Management/How-to-fill-insight-custom-field-with-insight-object-using/qaq-p/2016947

The trick for me was to just use the AQL from my lookup step in the edit issue step: objectType = Person and "Atlassian Account" = {{issue.reporter.accountId}}

@Robert Wen_Cprime_ I suggest pasting your AQL into the edit issue action and see if that works for you as well.

All comments

Robert Wen_Cprime_

Any Assets gurus out that can help me correct my thinking?

Rick Westbrock

I have rule which does set my Assets field "Site" based on the reference object in the Person object stored in the issue's Employee field. I'm setting the Site field by using {{issue.Employee.Site.Site ID}} where Site ID is the label attribute.

My current use case is using a lookup which doesn't use reference attributes but I am facing the same exact error no matter whether I try setting the Assets field to {{lookupObjects}}, {{lookupObjects.Key}} or {{lookupObjects."Employee ID"}} where Employee ID is the label attribute.

Apologies that this probably isn't helpful for you but maybe you will have better luck using the label attribute (instead of key) than I did. I will continue trying to figure this out on my side and will report back if I find a solution.

Rick Westbrock

The trick for me was to just use the AQL from my lookup step in the edit issue step: objectType = Person and "Atlassian Account" = {{issue.reporter.accountId}}

@Robert Wen_Cprime_ I suggest pasting your AQL into the edit issue action and see if that works for you as well.

Robert Wen_Cprime_

My requirements changed on this, so I don't need to set this up. Your answer seems correct.

tomasz.armata

That works like a charm. Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

addon-com.riadalabs.jira.plugins.insight

automation

jira-service-management-cloud

jira-service-management