Jira inventory management: items and stock

Use Jira to track individual IT items or record consumable quantities. Compare Assets, work items and an asset app, then choose where your inventory records should live.

Reviewed 2026-10-18

Jira can hold an IT inventory of individual items, including owners, locations, status and history, through Atlassian Assets on paid plans or an asset app. You can also record consumable quantities in Assets, but when purchasing or warehouse stock drives the process, a dedicated inventory system is usually the better system of record, linked to Jira work items (issues).

Two kinds of inventory

Before choosing a setup, separate the two jobs people call inventory management.

Individual items have their own identity. A laptop has a serial number, an assigned person and a location. You want to know which laptop someone has, whether it is in repair and what happened to it over time. Each physical item gets its own record.

Consumable stock is counted. For cables or toner, the useful question is how many units remain at a location. A quantity describes the stock; an individual record for every cable would usually add unnecessary work.

You may need both. Keep the distinction clear so that an equipment assignment does not become confused with a stock withdrawal.

Option A: Atlassian Assets

Assets is Atlassian’s native option for tracking things and linking them to Jira work. It is available on paid Jira plans without requiring Jira Service Management (JSM). Jira Free does not include Assets.

Atlassian is still rolling it out: the Jira pricing page says Assets objects are available to Standard and Premium single-site customers, with other customers to follow. Check your site before planning the setup.

For individual equipment, create object types such as laptops and monitors. Give each object attributes for its serial number, owner, location and status. Each laptop or monitor then has its own inventory record.

For consumables, use a number attribute for quantity. Decide what each record represents, for example one cable type at one location, and agree who updates the quantity. A count is only useful when people maintain it consistently.

Assets automation can respond to attribute changes through the Attribute Value Changed trigger, including changes to a quantity attribute. The Assets custom field connects inventory objects to work items, so a request can refer to the equipment involved.

If these records and links cover your needs, Assets is a reasonable place to start. Atlassian lists what Assets can do in plain Jira.

Option B: work items as inventory records

For a small equipment list, you can use one work item per physical item. Add custom fields for the serial number and owner, and agree how to record location and status.

This approach keeps the list within familiar Jira work. Its weakness is maintaining a clear equipment history and reliable counts: you need conventions that distinguish the item’s record from requests and tasks about it. Treat it as a simple register and assess the upkeep before expanding it.

Jira supports CSV import for work items. A Jira admin can use System → External System Import → CSV. The file needs a Summary column. This is a separate import route from importing objects into Assets.

Option C: a Marketplace asset app

A Marketplace asset app gives you a ready-made asset workflow inside Jira. Compare the functions you need and each app’s limits before choosing.

AssetPilot is made by Plugins Factory, the publisher of this page.

AssetPilot for Jira supports check-out and check-in to Jira users or external people, with due dates and overdue alerts. My assets gives people a view of their assigned equipment. Each asset has a QR code that opens its page in Jira.

CSV import creates locations as needed, and CSV export covers the current filter. Assignments cannot be set during import yet: check assets out after importing them. Version 0.1 supports 5,000 assets per Jira site.

Consumables with low-stock alerts are part of version 0.2, which is in Atlassian Marketplace review. See AssetPilot for details and availability.

Set up an IT inventory in Jira

Choose the record type first, then use the same basic preparation whichever route you take.

1. Define item types and fields. Separate laptops, monitors and other equipment where their records need different information. Start with tag, serial, owner, location, status, purchase date and warranty end. Agree which fields people must maintain.
2. Agree status names. An example set is Available, In use, Pending, In repair and Retired. Define what each means and who records a change. Avoid using different names for the same condition.
3. Prepare and import the current list. Remove duplicate records and make location names consistent. Use the asset inventory CSV template to organize the data, then follow the relevant route in import assets into Jira from CSV. Check how that route handles identifiers, dates and assignments.
4. Link items to requests. Make the equipment record easy to identify from the work about it. For Assets, use the Assets custom field. Keep the item’s identity consistent when someone reports a fault or requests a replacement.
5. Run a periodic stocktake. Compare records with the items held at each location and by each owner. Fix differences in ownership, location and status. For consumables, compare the recorded quantity with the physical count and investigate discrepancies.

Decide who owns these updates before importing. A complete starting list will still become unreliable if handovers and stock changes go unrecorded.

When another system should hold the inventory

If purchase orders, receiving, multi-warehouse stock or accounting valuation drive your process, assess a dedicated inventory system as the primary record.

This is a fit decision. Start with the transactions and controls your team needs, then choose where those records belong. Jira can remain the place for requests and follow-up work, linked to the inventory record.

For an IT team mainly tracking who has which device, Jira may be a good fit. For a team mainly managing stock movements and purchasing, evaluate that operational workflow first.

Choose your next step

Start by deciding whether you need individual item records, quantity records or both. Then compare the available routes in our Jira asset management guide. For more on the native option and plan availability, read does Jira have asset management?.