Missing proper AQL Search & Filters in Jira Assets?

[#1]

Hi Atlassian Community,

if you’re using Jira Assets, you’ve likely hit some roadblocks with AQL queries and reporting.

We’ve seen posts here about struggles like searching across all object types in a schema (e.g., JSDCLOUD-9908) or saving queries for reuse (e.g., JSDCLOUD-10829). These gaps make tasks like audits, inventory checks way harder than they should be.

Our team faced similar issues:

• Spending a lot of time hunting for exact object types/attributes or correcting typos in AQL.

• Large result sets (across many objects) that were difficult to filter or explore without a good UI, often requiring clicking through asset types one by one.

• Schema mismatches slowing down even experienced admins.

We know there’s the Confluence Assets Macro, which is a useful option for reporting in Confluence. But in practice, it didn’t fully meet our needs:

• It only works for one schema per macro at a time, which makes cross-schema audits or dependency mapping cumbersome.

• It’s more suited for static reports and documentation, rather than dynamic exploration or operational checks inside Jira.

• Queries aren’t easily reusable across different teams or workflows. Sharing it with others often meant copying the macro, adjusting it, or even recreating the page — which can get lengthy. If you’re not careful, it’s easy to accidentally alter the report or selected columns while experimenting with new AQL (as columns reset to defaults when adjusting AQL).

We agree it would be great if Atlassian provided this directly in Jira Assets. Until then, we’ve found value in extending the functionality ourselves and we thought it would be helpful to share our approach, not as a definitive solution, but to illustrate one way to handle these challenges.

To address this, we built an App combining a Visual Board for AQL results and a natural language query Rovo Agent.

• Visual Board: Lets us explore results, apply filters across schemas, and save queries for reuse.

• Natural Language Queries (Rovo Agent): We can type something like “Show all Dell laptops bought this year” or “Find licenses expiring in 90 days”, and it generates AQL automatically, mapping terms to the schema. Also showing the list of results from AQL.

We are using it for tasks like identifying unassigned devices, mapping app dependencies, or checking compliance data. It might come handy when someone needs a query but isn’t familiar with the schema.

Since these pain points seem common, we’re sharing this to open the discussion.

• How are others handling AQL challenges today?
• Are you using custom scripts, exports, the Confluence Assets macro, or something else?

Any ideas or approaches would be great to hear!

Cheers,

Matej Štrba / Sykora IT Team

P.S. You can check our docs to see our approach, but mostly, let’s swap ideas!