[Feature Request] Native Jira Assets AQL tool for Rovo Agents — enable dynamic CMDB queries

Question

Posting this as a question since there's no suggestion option available — but this is meant as a feature request for the Rovo team. Hi everyone, We've been trying to build a Rovo Agent that helps users navigate JSM requests — things like "who handles Azure requests?" or "which group should I pick for this category?" The data for this lives in Jira Assets (support group members, routing rules, application ownership). It's all nicely structured in our object schemas and shown on Confluence pages via AQL macros. The problem? Rovo can't read AQL macro content. It just gets an empty placeholder. So the agent is essentially blind to all that CMDB data. To work around this we'd need to either copy the data into static Confluence tables (which defeats the whole point of having a CMDB) or set up scheduled automations to render it elsewhere. Not ideal. What we'd love to see: A native Assets AQL tool in Rovo Studio — so an agent can just run queries like: // Which support group is a specific user a member of? objectType = "Groups" AND "Users.Name" = "John Doe" // Which group is responsible for a specific application? objectType = "Application" AND Name = "SAP" HAVING outboundReferences("Group")...and get back real, live data from Assets to answer routing questions directly in the chat. This would be a game changer for anyone using JSM + Assets as a CMDB. Incident triage, request routing, CI ownership lookups — all suddenly possible with a Rovo Agent. Would love to know if others have hit the same wall, and whether this is on the roadmap at all! 🙏

Arkadiusz Wroblewski · Answer

Hello @Svetlana Risteska

Also proper for feature requests are always the Feedback button or creating a ticket at support, and then if they won't find a matching JAC, they create a feature request.

Atlassian Team members track the Community forum, but be sure to give feedback in specific channels if you want things addressed.

Best,

Arek 🤠

Rebekka Heilmann (viadee) · Answer

Yes! To clarify: Almost all new features will have some form of feedback button (mostly a small megaphone icon) built into the product itself. The feedback there will be sent to the correct product team.

Feature requests on here rarely reach the correct person as not a lot of Atlassians are reading Q&A on here, sometimes not even the comments on their own posts. That's unfortunate but the truth.

If you can't find the feedback button, you could always open a regular support request and ask the support to open a JAC Ticket. There are already a few items related to Assets and Rovo: [ROVO-940] "Search Assets Data" skill does not return all attributes - Create and track feature requests for Atlassian products.

Onur Mert Gürses · Answer

Hello,

You might want to try using Feedback for this. It could be more helpful.