Assets is real, and it's plan-gated
Jira Service Management's asset and configuration management capability is called Assets, previously branded Insight. It lets you model objects, servers, licenses, contracts, laptops, or anything else your schema defines, with custom attributes and relationships between them: a CMDB built into JSM rather than a bolted-on marketplace app. It's a genuinely capable feature. The catch is availability: Assets ships on the Premium and Enterprise tiers of Jira Service Management only. Free and Standard sites don't have it.
What a Free or Standard site sees instead
On a plan below Premium, there's no Assets workspace at all: no object schemas, no AQL search, nothing to configure. It isn't a locked or greyed-out feature you can preview; it simply isn't present in the product for that plan. A tool built to work with Assets should recognize this and say so plainly rather than showing a blank or broken screen, since the fix isn't a configuration change, it's a plan change.
What you actually need to use it
- A Jira Service Management site on Premium or Enterprise.
- An account with Assets permission on at least one object schema, since schema-level permissions are separate from general JSM access.
- At least one schema that actually contains objects, since an empty schema has nothing to report on yet.
Once you're on the right plan
Assets adds object types with custom attributes, an object schema per domain (a hardware register, a software license catalog, a contract log), reference attributes linking objects to each other, and a query language (AQL) for filtering. What it doesn't include is a general export or bulk-edit path built for those object attributes: Jira's standard Excel and Sheets export was built for issues, not Assets objects, and leaves custom attribute columns blank when pointed at an Assets view.
Once Assets is available
See how to export Jira Service Management Assets to Excel for the first thing most teams want to do with it.
Built for Assets specifically
Assets Excel Sync requires a Premium or Enterprise JSM site with an Assets workspace, and talks to the Assets API directly, so every attribute exports and imports intact rather than through the general Jira export path that leaves custom fields blank. It's built by Cody Labs and is not affiliated with Atlassian.
See Assets Excel Sync for Jira Service Management