How to Show Users Their Assigned Assets in Jira Service Management

Step by step: give employees and JSM portal customers a My Assets view of their own laptops and licenses, filtered by currentUser() in AQL. Plus alternatives.

Jira Service Management Assets knows exactly which laptop, license and contract belongs to whom — but the people it describes rarely see it. Employees don't know which device is registered under their name, which licenses they hold or when something expires, so they open tickets to ask, and IT looks it up by hand.

This guide shows how to show users their assigned assets in Jira and on the JSM customer portal with My Assets in Assets Gadgets: every person sees only their own objects, filtered by currentUser() in AQL, without access to the Assets schema. Setup takes about 15 minutes. Alternatives without an app are at the end.

An earlier version of this article appeared on the Atlassian Community (App Central).

What your users will see

My Assets is a personal view of the Assets objects that point to the viewer — laptops, licenses, phones, contracts. It is available in four places, all from the same setup:

Where How people open it Who
Jira Asset Manager in the Jira apps menu, tab My Assets Jira users
JSM customer portal Portal user menu → My Assets Customers and unlicensed users
Jira dashboard The My Assets gadget Signed-in dashboard viewers
Rovo The My Assets Assistant agent Users with Rovo

My Assets Overview: a card per asset type, recently updated assets, counters and Needs attention

My Assets Overview: everything assigned to me, on one page

The Overview tab shows one card per table with counts and the latest assets, Recently updated, and a right column with counters, Assets by category, a status bar and Needs attention — assets whose end, expiry, renewal, warranty or due date is within 30 days. Each table also has its own tab with search, filter chips, a Table / Cards switch and a details panel.

How the filtering works

You define My Assets as a list of tables, each with its own AQL. In that AQL, currentUser() (or {{currentUser}}) is replaced by the person who is viewing, so everyone gets only their own rows:

objectType = "Laptop" AND Owner = currentUser()

If the attribute is a reference to a person object rather than a user field, go one level deeper:

objectType = "Laptop" AND "Owner"."Atlassian Account ID" = currentUser()

What this guarantees:

  • People see only the tables, columns and objects you configured — not the whole schema.
  • People cannot run their own AQL.
  • My Assets has its own rules and does not depend on the app's Data Display Mode, so portal customers without Assets access still see their own objects.
  • Anonymous visitors never count as signed in and get no data.

Step 1: Open the My Assets settings

  1. In Jira, go to administration and open Assets Gadgets — Settings (it is listed with the other installed apps). Only Jira administrators can open it.
  2. Select the tab My Assets (Portal).

The My Assets (Portal) settings: Overview first, then the tables in tab order

Overview first, then your tables in tab order

Overview is always the first tab. Your tables follow in the order shown; drag the ⋮⋮ handle to reorder them. You can add up to 10 tables.

Step 2: Add a table with currentUser() AQL

  1. Select Add table.
  2. On the Data sub-tab, enter a Tab title, for example "Laptops".
  3. Enter the AQL filter with currentUser(), as in the examples above.
  4. Select Validate / Load columns. The header shows Valid AQL or AQL error.
  5. Under Columns, use Choose a column to add, drag columns into order, and remove the ones people don't need. The same order is used in the table and in the cards.

Table editor, Data sub-tab: tab title, AQL filter with currentUser() and the column list

Data: the AQL that decides whose assets appear

Add one table per kind of asset — Laptops, Licenses, Phones — so each gets columns that make sense for it.

Step 3: Add counters and insights (optional)

On the Insights sub-tab you can add up to 10 KPI counters per table, each with an optional highlight, and a breakdown chart grouped by an attribute (for example by status or model). People open them with Show insights next to the table.

Table editor, Insights sub-tab: KPI counters and the breakdown chart

Insights: counters and a breakdown per table

For the Overview tab itself, the Overview editor sets up to 3 counters for the right column and what happens with tables that have no rows for a person: Always show them, Hide from the Overview tab only or Hide everywhere (tab and Overview).

Step 4: Let people raise a request about an asset (optional)

On the Requests sub-tab:

  1. Turn on Show Create request in the asset details.
  2. Choose a Service desk, then a Request type. You can add up to 5 request types.
  3. Optionally, enter a Button label of up to 40 characters, such as "Report a problem".

Table editor, Requests sub-tab: service desk and request types for Create request

Requests: a button in the asset details opens the JSM form

You need agent access to the service project to pick its request types. The request form then shows "Request about: {object}", the person selects the same asset in the form's Assets field, and the asset key is saved with the request.

Step 5: Limit tables to groups and save

On the Access sub-tab, Visible to groups limits a table to members of the chosen groups — for example, a "Company phones" table only for the sales group. Empty means everyone who can open My Assets.

Table editor, Access sub-tab: Visible to groups

Access: who sees this table

Select Save. The settings check the setup first and list what to fix — a table without AQL or columns, Create request without request types, or more than 10 tables — with links to the right sub-tab.

The Details panel sub-tab is optional too: up to 30 Asset timeline rules choose which history entries people see in the details of an asset.

Step 6: Check it as a user

Open My Assets the way your users will:

  • In Jira: Asset Manager → My Assets.
  • On the portal: the user menu → My Assets. It opens in a large window.
The JSM portal user menu with the My Assets item

Portal user menu → My Assets

Click a row or card to open the details panel: Open in Assets, Create request, Summary, Your requests, Related assets and the Asset timeline.

My Assets on the JSM customer portal with tables, insights and the details of an asset

What a portal customer sees

If you see Nothing to show here yet, no asset points to your account in the attribute your AQL uses — check that attribute on one of your objects. My Assets isn't set up yet means no tables are saved.

Alternatives without an app

Automation and email. A scheduled Jira automation can pull users from a group via Send web request, run Lookup objects with AQL such as objectType = Laptops AND Owner = {{user.accountid}} for each user, and email the result. It works with built-in tools, but it needs an API token in the rule, gets complex across several schemas, and sends a static snapshot that lands in the inbox, not a live view.

An Assets field in the request form. A custom Assets field with AQL filtered to the reporter lets people pick their device when they open a ticket ("report a broken laptop, pick yours"). It helps at the moment of the request, but it gives no overview of what someone has. My Assets combines both: the overview, and Create request from the asset.

FAQ

How do I show users only their own assets in JSM?

Add a table in Assets Gadgets — Settings → My Assets (Portal) with an AQL filter that uses currentUser(), for example objectType = "Laptop" AND Owner = currentUser(). The app replaces currentUser() with the viewer, so each person sees only the objects that point to them.

Do portal customers need an Assets license or Jira license?

No. Customers and unlicensed users open My Assets from the portal user menu. My Assets uses its own rules and does not depend on the app's Data Display Mode.

Why does My Assets say "Nothing to show here yet"?

No asset in the configured tables matches the viewer. Check that the person is set in the attribute your AQL uses with currentUser(), and that the AQL has no stray apostrophe before currentUser().

How many assets and tables can My Assets show?

Up to 10 tables plus Overview, and up to 500 rows per table. Filters apply to those 500 rows; split very large tables into narrower ones with their own AQL.

Can users see other people's assets?

No. Every table is filtered by currentUser(), people cannot change the AQL, and tables can be limited to groups with Visible to groups.

Can employees raise a ticket about a specific laptop?

Yes. Turn on Show Create request in the asset details for the table and add 1–5 request types. The request form shows which asset it is about, and the asset key is saved with the request.

Set up My Assets

Install Assets Gadgets from the Atlassian Marketplace — free for up to 10 users — and add your first My Assets table. Every setting is described in the Assets Gadgets user guide and in the My Assets documentation.