Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to fill insight custom field with insight object using automation

Petar Milavić May 2, 2022

Hi all,

after the issue creation, I want to set an insight custom field with some insight object using automation.

Lookup objects part works fine: 




If I select the attribute from the lookup object that works fine and the Summary field is filled:




But If I try to fill the custom insight field with an Insight object that action returns

An error occurred while requesting remote information
Bad Request
No fields or field values to edit for issues (could be due to some field values not existing in a given project)
and the custom insight field remains empty. This is the configuration part:




Is there some simple solution to set the insight field with an insight object?

Thank you,


3 answers

1 accepted

8 votes
Answer accepted
Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 2, 2022

Hey @Petar Milavić ,

The Edit action you are using is expecting an IQL where you entered the {{lookupObjects}}

I suggest using the IQL you used to do the LookupObjects action in the Edit action. That should be enough.

1 vote
Aleksandra Leesment May 8, 2024

If you have one object then the field should be:

key = {{lookupObjects}}

If it's multiple objects, then:

key in ({{lookupObjects}})

Alan Bruce May 16, 2024

Hello @Aleksandra Leesment 

Do you know if this resolves getting the following error:

Edit issue
An error occurred while requesting remote information
Service Unavailable

I normally use the 'Edit issue' and then set the Asset Custom field using:

Name = Helpdesk

This seems to work most of the time but every once in awhile I will get the 'Service Unavailable' error in the Audit log. 

Aleksandra Leesment May 28, 2024

This error usually occurs when there is an issue with Jira Service Management product. There were some incidents on 14th and 15th May (, which might've caused it. I recommend reaching out to Atlassian Support if this error keeps happening.

Alan Bruce May 28, 2024

Thank you

Like Aleksandra Leesment likes this
0 votes
Petar Milavić May 2, 2022

Hi @Dirk Ronsmans

thank you very much, it works.



Tania van Wyk de Vries August 24, 2022

Can you share your final solution on the edit Insights field?

Tania van Wyk de Vries August 24, 2022


Like Yasmin Romero Gutierrez likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events