Turn Jira Service Management Assets into dashboards and reports. AQL counters, pie, donut, bar and date charts, tables, asset search with CSV export, and a My Assets view so employees and portal customers see their own assets
JSM's Assets module is one of the most powerful CMDB features in any service management tool — but its out-of-the-box dashboards are limited to flat tables. Assets Gadgets turns AQL queries into real dashboards: counters, charts, comparisons, and a customer-facing portal where end-users can browse their own assigned resources.
AQL counters, pie, donut, bar, stacked and date charts, tables, Data Quality and Expiring Soon gadgets. Pick your own chart colours and drill down from any value to the matching objects
Each person sees the assets assigned to them in Jira and on the Jira Service Management portal: overview cards, filters, insights, asset details and Create request with the asset already linked
Asset Manager searches Assets with filter chips or AQL with suggestions. Save and share filters, reuse them in every gadget and export results to CSV for reports
AQL (Assets Query Language) is Atlassian's filter syntax for the Assets module. Most gadgets work with pre-built AQL templates, so basic usage requires no AQL knowledge. Advanced filters use simple patterns like `objectType = "Server" AND status = "Active"`.
Yes — that's the default. In Data Display Mode, "Respect Permissions (Recommended)" fetches data as the viewing user, so each person sees only objects they can access. Admins can switch to "Unrestricted (All Data)" for shared dashboards where everyone should see the full result.
Use currentUser() or {{currentUser}} in the table's AQL filter — the query then resolves to the signed-in portal user. Tables can additionally be restricted to specific Jira groups.
Ten: AQL Counter, Pie, Donut, Bar, Horizontal Bar, Stacked Bar, Horizontal Stacked Bar, Assets Table, Results Table, and the Date vs Date chart — all driven by AQL queries against your Jira Assets data.
Yes. Admin-tunable performance settings control how much a gadget loads (default 20,000 objects per gadget, configurable up to 200,000), plus page size, parallelism and a fetch time budget — so dashboards stay responsive on big schemas.
Inside your Atlassian site. The app is built on Atlassian Forge and reads your Assets data through Atlassian's APIs — it keeps no external database of your assets.