Assets Gadgets release notes — August 2026

Ask Rovo about your assets — the My Assets Assistant answers questions about devices, licences and tickets. Plus My Assets inside Jira, in a fresh card look.

Three things in this release, and each one meets your people where they already are.

AI for your assets: the new My Assets Assistant is a Rovo agent that answers questions like "What devices are assigned to me?" or "Were there any tickets about my laptop?" — right in the Rovo chat in Jira.

My Assets now lives inside Jira, too: no longer only in the Jira Service Management portal, it's a global page your employees open straight from the Apps menu — same configuration, nothing to set up twice.

And it looks the part: the view got a visual refresh with layered cards, colour-coded KPI tiles and bigger, clearer counters.

Meet the My Assets Assistant

Open the Rovo chat in Jira, pick My Assets Assistant, and ask about your assets in plain language — in your own language, too. The assistant can:

  • Give an overview — every table you can see in My Assets, with your devices, licences and other items.
  • Find a specific asset — by name, key or any attribute value ("find my MacBook", "which monitor is in the Berlin office?").
  • Tell an asset's full story — the same detail you see in the My Assets panel: attributes, the asset timeline, related assets, and your reported tickets for it, both open and resolved. So "were there tickets about my laptop?" gets a real answer, with links.

The assistant only ever answers from live data in your site, and it sees exactly what you see in My Assets — the same tables, the same group-based visibility your admins configured, the same ticket visibility. It cannot look up other people's assets, and it says so if asked.

NOTE: The assistant requires Rovo to be available on your site. Answers are grounded in your My Assets configuration — if the portal isn't set up yet, the assistant will tell you to ask your Jira admin instead of guessing.

Your assets, your privacy

The assistant runs entirely on Atlassian infrastructure: the AI is Atlassian's own Rovo, the data access is the same Forge backend that powers My Assets, and no asset data is sent to any third-party service. The app keeps its Runs on Atlassian status, and this release required no new permissions.

Build your own agents with My Assets tools

For teams that build custom Rovo agents in Rovo Studio, the same three capabilities — overview, search, and full asset details — are now available as My Assets tools. Combine them with your own instructions to build, say, an onboarding helper or a hardware-refresh assistant that works with the assets each user is allowed to see.

NOTE: Rovo Studio tools for apps are an Atlassian preview feature and may still change on Atlassian's side.

My Assets inside Jira — not just the JSM portal

Until now, My Assets lived in the Jira Service Management portal. With this release it's also a global page inside Jira: your employees find My Assets in the Apps menu — with the app's own icon — and get the full experience rendered right into the page, no portal detour and no pop-up window.

It's the same view, powered by the same configuration: the tables, KPI counters, charts and group-based visibility you set up once apply to both surfaces. Nothing to configure twice — if My Assets is set up for your portal, it already works inside Jira. That's ideal for teams whose people live in Jira all day and rarely open the JSM portal.

A fresh look for My Assets

My Assets — in the JSM portal and on the Jira global page — now uses a layered, card-based design:

  • Panels (search, tables, the detail panel, statistics) float as white cards on a subtly sunken background, so the page reads at a glance.
  • KPI tiles are colour-coded — each counter has its own accent tint, and the numbers are bigger and easier to scan.
  • More breathing room throughout: wider column gaps, clearer separation between tabs and content, and the Table/Cards switch no longer crowds the detail panel.
  • The welcome screen preview got the same treatment, so what new users see is what a configured portal actually looks like.

Under the hood, this release also includes internal improvements to product analytics and licensing checks — nothing you need to configure, and nothing that changes what data the app can access.

FAQ

What can the My Assets Assistant answer?

Anything grounded in your My Assets view: which assets, devices and licences are visible to you, details of a specific asset (attributes, asset timeline, related assets), and the tickets you reported for it — open and resolved. It always answers from live data, never from memory.

Can the assistant see other people's assets?

No. It uses the same visibility rules as My Assets itself — the tables your admins configured and their group restrictions. Every answer is scoped to the person asking; requests about other users are declined.

Does asset data leave our Atlassian site when we use the assistant?

No. The AI is Atlassian's own Rovo, and the data access runs in the app's Forge backend on Atlassian infrastructure. No asset data is sent to third-party services, and the app keeps its Runs on Atlassian status.

How do I start using the My Assets Assistant?

Open the Rovo chat in Jira (the Ask Rovo button), choose My Assets Assistant from the agent list and ask away — for example "What assets are assigned to me?". There is nothing to configure in the app; it works as soon as My Assets is set up.

How do employees open My Assets without the JSM portal?

In Jira, open the Apps menu and choose My Assets — the same view as in the portal, using the same configuration and visibility rules, rendered directly inside Jira.

How do I use the My Assets tools in my own Rovo agent?

In Rovo Studio, add the My Assets tools to your custom agent — they provide asset overview, search and full asset details, always scoped to the person talking to the agent.

Do I need to reconfigure anything for the new My Assets design?

No. The refresh is purely visual — your tables, columns, KPI counters and charts stay exactly as configured, in the portal and on the global page alike.

How do I ask Rovo which assets are assigned to me?

Open the Ask Rovo chat in Jira, pick My Assets Assistant and type "What assets are assigned to me?" — or just "my devices". The answer lists what you can see in My Assets, with links to each asset.

How do I check whether there were support tickets about my laptop?

Ask the assistant "Were there any tickets about my laptop?". It returns the requests you reported for that asset — open and already resolved — with links, so you don't have to search the portal yourself.

Can I ask about my assets in my own language?

Yes. Ask in plain language in the language you speak — the assistant understands and answers in kind, the same way the localized My Assets portal follows your Atlassian language setting.

How do I find an asset by serial number, location or another attribute?

Ask for it directly — "which monitor is in the Berlin office?" or "find the device with serial C02FQ3ABCDE". The assistant searches by name, key or any attribute value you're allowed to see, then can give you that asset's full details, timeline and related assets.

Do I need Rovo to use Assets Gadgets?

Only for the assistant. Dashboard gadgets and the My Assets view — in the portal and on the new Jira global page — work without Rovo; the My Assets Assistant is the one feature that needs Rovo available on your site.

Does this release need new permissions or an admin setup?

No. The release added no new permissions, and there is nothing to configure: if My Assets is set up, the assistant, the Jira global page and the refreshed design are all there.

Ask your assets something

Open Ask Rovo, pick the My Assets Assistant, and start with "What assets are assigned to me?" — then try the question your service desk hears every week.

👉 Assets Gadgets for Jira — Dashboards & Reporting