Jira asset management: choose your approach

Compare Atlassian Assets, Marketplace apps and a spreadsheet approach. Choose by your Jira plan, record count and the workflows your team needs.

Reviewed 2026-10-18

There are three ways to do asset management in Jira Cloud: Atlassian’s Assets app, an asset app from Atlassian Marketplace, or work items (issues) and a spreadsheet. Assets is now included in paid Jira plans and in Service Collection Standard and above, while Atlassian completes its rollout. The right route depends on your plan, how many records you keep and whether you need service management features.

What asset management in Jira covers

An asset register brings together the things your team needs to track: hardware, software licences and equipment. Each record should show who has the item, where it is, its lifecycle status and its history. Linking that record to requests, incidents and tasks gives people context when they work on it.

Start by deciding what belongs in your register and who will maintain it. For a closer look at the scope of an inventory, see using Jira for inventory management.

Option 1: Atlassian Assets

Assets tracks objects and their relationships, then links them to work in Jira. It suits teams that want a flexible schema and are comfortable deciding how their records should be structured.

What paid Jira includes

Since 1 September 2026, paid Jira plans include Assets with an allowance of 1,000 objects per organization. Jira Free does not include Assets. The rollout began with single-site organizations: the pricing footnote specifies Standard and Premium single-site customers, with additional customers still rolling out. Atlassian lists multi-site rollout for the next calendar year, so check your organization’s access before committing to this route. The Jira pricing page and Assets licensing FAQ give the details.

A paid Jira site does not need Jira Service Management (JSM) to use Assets. In plain Jira, you get schemas, object types, objects, attributes, references and statuses. You can search with AQL, import and export data, make bulk edits, use Assets automation and add an Assets custom field to work items.

Plain Jira does not include portal and request workflows, Data Manager, Assets dashboards or Assets Discovery. If you need those, compare the service management plans rather than assuming the Jira allowance includes them. Atlassian’s known limitations at Jira launch lists the boundary, and our guide does Jira have asset management? covers it plan by plan.

What Service Collection adds

Jira Service Management and Service Collection include 5,000 objects on Standard, 50,000 on Premium and 500,000 on Enterprise. Free does not include Assets. Service Collection Standard includes asset discovery, a service registry and dependency mapping; Hardware Asset Management and Data Manager are Premium and Enterprise features. Service Collection pricing lists the plan differences.

Native Assets is a strong candidate if your team already uses JSM or Service Collection, needs relationships between objects, or wants to design a register around its own structure. Allow time to define object types, attributes and references, and assign someone to maintain that structure.

Allowances and extra usage

Above the included allowance, Assets costs $0.02 per object per month, with volume discounts for prepaid packs (as listed on 18 October 2026). Plan prices vary by user count and billing cycle.

Allowances pool across subscriptions at organization level. Count all the things you intend to track, rather than treating each schema as a separate allowance. One object is one tracked thing; attributes and references do not count separately, and schemas are free.

If you reach the allowance with extra usage turned off, new objects, imports that add objects and automation that creates objects pause. Existing objects remain usable. For new Assets customers after 1 September 2026, and for existing monthly customers, Atlassian starts extra-usage billing on 3 December 2026. The Assets licensing FAQ has the counting, pooling and billing rules.

Option 2: a Marketplace asset app

An asset management app or plugin can suit teams that want a ready-made register and workflows such as check-out. Compare the setup, daily assignment process and record maintenance each app supports. Requirements for JSM depend on the app.

Marketplace apps are billed on the host product’s user tier, not the number of assets. The licence covers that whole tier even if only some people use the app, and with Jira and JSM on one site the higher tier applies. Atlassian’s Marketplace licensing FAQ explains the rule.

This route is worth evaluating if you use Jira without JSM, or prefer an established register structure over designing an Assets schema. Check the app’s record limits separately from its user-based licence.

AssetPilot for Jira

AssetPilot is made by Plugins Factory, the publisher of this page. It keeps asset inventory, ownership and lifecycles in Jira Cloud and does not require JSM. Setup offers IT equipment, Office and Lab templates, or a blank start.

• Check-out and check-in to Jira users or people without a Jira account, with due dates, overdue alerts and a My assets view.
• A panel on each work item shows its linked assets and the reporter’s devices.
• CSV import with suggested mapping, a validation preview and updates matched on tag or serial. Assignments can’t be set during import yet.
• A QR code on every asset that opens its page in Jira.
• Data stays in Forge storage in your Jira site’s region, with no external calls.

Version 0.1 handles up to 5,000 assets per Jira site. See AssetPilot for details and availability.

Option 3: work items and a spreadsheet

A spreadsheet register with related Jira work items can be enough for a few dozen items when you do not need lifecycle tracking or asset history. It gives you a place to list equipment and a way to track tasks about it.

The limitation is keeping the two sources current. This approach does not provide a single asset record with its history: someone must reconcile assignments, locations and changes between the sheet and the work items.

Jira supports work-item CSV import if you choose this route. It requires a Jira administrator and a Summary column. Importing work items does not turn the spreadsheet into an asset register with lifecycle history. See Atlassian’s CSV import documentation.

How to choose

Use these questions to narrow the choice before comparing software in detail.

1. Which plan are you on, and has Assets reached your organization? If paid Jira already gives you Assets, evaluate it first. If you already use JSM or Service Collection, include the native service management features in that assessment.
2. How many records will you maintain? Compare the count with Jira’s 1,000-object allowance or Service Collection Standard’s 5,000-object allowance, including pooled subscriptions. Above your allowance, price the extra usage. For any app, check its own asset limit.
3. Do you need service management or discovery? Compare Service Collection when you need those features. Assets in plain Jira does not include portal and request workflows or Assets Discovery.
4. Do you need check-out and due dates? Evaluate apps with those workflows, and compare their setup with the work required to design your native register.
5. Who will maintain the records and structure? A team prepared to own a schema should consider Assets. A team seeking predefined workflows should evaluate apps. A small list with no lifecycle or history needs may stay in a spreadsheet.

Get started with your asset register

Prepare the same record set before testing your preferred route. It will make missing fields, duplicate records and maintenance responsibilities easier to spot.

1. Count and clean your records with the asset inventory CSV template. Identify what you track and which fields each record needs.
2. Estimate the licence and object costs with Jira asset management pricing. Use your organization’s subscriptions and Jira user tier.
3. Follow import assets into Jira from CSV for your chosen route. Check identifiers and mappings before importing your full register.