Assets Gadgets adds advanced dashboard gadgets to Jira Assets. Build custom AQL counters reports, interactive tables and bar, horizontal/stacked and donut charts, plus date vs date comparisons to track and analyze asset metrics in real time.
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.
Allow users to securely view their assigned devices, licenses, and contracts directly in the Jira Service Management portal using controlled AQL filtering with currentUser().
Use interactive pie charts and results tables to explore your Jira Assets data by department, manager, role and more. Filter with AQL queries to drill down into any attribute.
Build custom dashboards with bar charts, line charts and donut charts to count assets, monitor statuses, and compare updates versus expiration dates using AQL queries.
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.