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; } } }

Rovo does not read the correct asset values

Martina.Bruehl

Hi,

I keep running into the same problem with several agents, reading the correct values from asset attributes.
Even if I specify the schema and the exact field name and ID in the instruction, the correct values almost never get returned, either it comes back empty or with a wrong value.
Does anyone know this problem or have a suggestion?

Accepted answers

Evgenii

Hi @Martina Brühl,

Do your agents have the Search Assets data skill enabled? Without it the agent can't query Assets at all and just makes things up. Enable it in Rovo Studio and scope it to your schemas. Yo can read more details here:

https://community.atlassian.com/forums/discussion/3241671/your-assets-data-at-your-fingertips-with-rovo

If it's already on, read the comments under that announcement, several people report exactly your symptoms: only part of the attributes come back, the rest gets invented, field IDs in instructions don't help. Known problem, the Assets PM is collecting cases there, worth adding yours.

Until it's fixed, you can pull attribute values via Assets REST/AQL directly where correctness matters.

Anwesha Pan

Hi @Martina Brühl

This is a very common issue when building and instructing Rovo agents to interact with Jira Assets (formerly Insight / CMDB). Even when you specify the schema and exact field names or IDs in the instructions, agents frequently return empty or incorrect values due to a few underlying architectural reasons and how LLMs interact with the Assets API and AQL.

To fix this across your agents, update their system instructions with the following rules:

Enforce Dynamic Attribute Discovery:
"Before querying or extracting values, always inspect the object type schema using assets_list_obj_type_attribute to confirm the exact attribute name, type (DEFAULT, REFERENCED_OBJECT, USER), and referenced object type ID."
Handle References Explicitly:
"If an attribute is of type REFERENCED_OBJECT, do not expect a raw string. Use dot notation ("Attribute Name".Name) for outbound references, or check if the relationship is modeled as an inbound reference (object having inboundReferences(...))."
Quote All Multi-Word Attribute Names in AQL:
"Always wrap attribute names containing spaces in double quotes in AQL queries (e.g., \"Operating System\" = \"Linux\")."
Scope by Schema ID:
"Always prepend AQL queries with the specific schema identifier: objectSchemaId = <ID> AND objectType = \"<TypeName>\"."
Value Extraction Guidance:
"When reading attribute values from API responses, inspect both displayValue and value properties. For User attributes, resolve the Account ID (AAID) to the user's name if displaying in text."

Hope this answers your question.

Thanks,
Anwesha

All comments

Evgenii

Hi @Martina Brühl,

https://community.atlassian.com/forums/discussion/3241671/your-assets-data-at-your-fingertips-with-rovo

Until it's fixed, you can pull attribute values via Assets REST/AQL directly where correctness matters.

Anwesha Pan

Hi @Martina Brühl

To fix this across your agents, update their system instructions with the following rules:

Enforce Dynamic Attribute Discovery:
"Before querying or extracting values, always inspect the object type schema using assets_list_obj_type_attribute to confirm the exact attribute name, type (DEFAULT, REFERENCED_OBJECT, USER), and referenced object type ID."
Handle References Explicitly:
"If an attribute is of type REFERENCED_OBJECT, do not expect a raw string. Use dot notation ("Attribute Name".Name) for outbound references, or check if the relationship is modeled as an inbound reference (object having inboundReferences(...))."
Quote All Multi-Word Attribute Names in AQL:
"Always wrap attribute names containing spaces in double quotes in AQL queries (e.g., \"Operating System\" = \"Linux\")."
Scope by Schema ID:
"Always prepend AQL queries with the specific schema identifier: objectSchemaId = <ID> AND objectType = \"<TypeName>\"."
Value Extraction Guidance:
"When reading attribute values from API responses, inspect both displayValue and value properties. For User attributes, resolve the Account ID (AAID) to the user's name if displaying in text."

Hope this answers your question.

Thanks,
Anwesha

Martina.Bruehl

Thanks, good to know it's not a layer 8 problem.

Martina.Bruehl

Hi Anewsha,
Thank you — that helped immensely. I'm not quite there yet, but it's much better than before.

Anwesha Pan

That's awesome @Martina Brühl! Thanks for letting me know 🙂

Welcome!

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

Quick Links

Find more posts tagged with

assets

rovo

rovo-agent