Blog ·

Asset management for Jira: the register, the audits, and the renewals

Asset management for Jira comes down to two questions: where does the list of assets live, and who checks it on time? Jira Service Management has a built-in register called Assets for the first. The second is the part teams lose: the quarterly inventory count, the warranty that lapses unnoticed, the software license that renews at full price because nobody reviewed it. This guide covers both. It shows where the register can live depending on your plan, then sets up the recurring checks as tickets that appear on their own.

Statements about Atlassian's plans and features are as of October 2026, from Atlassian's own pricing and feature pages.

Where the asset register can live #

An asset register is a list of things the organisation owns or pays for, each with an owner, a location or system, and the dates that matter: purchase, warranty end, renewal. There are three common homes for it when the team already works in Jira.

Option What it is Good for What to watch
Assets in Jira Service Management Atlassian's own object database, linked to requests and incidents IT teams already on a paid service plan Object allowance per plan
A Jira project used as a register One work item per asset, with custom fields Small estates, teams on Jira Software only Search and reporting stay basic
A dedicated asset tool, linked from Jira Your endpoint manager or IT asset tool Large estates with discovery and scanning Two systems to keep in step

Whichever you pick, the register is only half the job. A list that nobody reviews drifts within a quarter: laptops change hands, contracts renew, a server is retired but still listed. The checks are what keep it true, and the checks are routine work that repeats on a calendar.

What Atlassian includes with Assets #

Atlassian's pricing page puts it plainly:

Asset and configuration management is included in Service Collection Standard, Premium and Enterprise plans.

The Free plan is not on that list. Each paid plan comes with an object allowance, and the same page sets it out:

Plan Assets objects included Notes from Atlassian's page
Standard 5,000 Core asset and configuration management
Premium 50,000 Adds Data Manager and Hardware Asset Management
Enterprise 500,000 Everything in Premium

Above the included amount, Atlassian lists extra objects starting at $0.02 (USD) per object per month, with volume discounts. An object is one record: a laptop, a license, a contract, a server. If you model each laptop, its user and its warranty as separate objects, count all three.

If you are on Jira Software alone, Assets is not part of your plan. The project-as-register approach below works there, and it is how many small teams start.

Set up the register as a Jira project #

When Assets is not available, or the estate is a few dozen items, a plain Jira project does the job.

  1. Create a team-managed project named Assets with a single work type, Asset.
  2. Add fields for the facts you check: owner, category (laptop, license, contract, server), serial or account number, warranty end, renewal date and cost centre.
  3. Use statuses for the lifecycle: In use, In storage, In repair, Retired.
  4. Save a filter per category, and one for anything whose renewal date falls in the next 60 days.

That last filter is the heart of it. In JQL it reads like this, assuming a date field named Renewal date:

project = ASSETS AND "Renewal date" <= 60d AND status != Retired ORDER BY "Renewal date" ASC

A filter answers the question when somebody asks it. Somebody still has to ask it, every month, and that is the routine the next section turns into tickets.

The recurring checks that keep it true #

These are the checks most asset owners run, with a cadence that suits a small or mid-sized team. Adjust to your audit requirements.

Check Cadence What the ticket asks for
Renewals due in the next 60 days Monthly Review each item in the filter, decide renew, downsize or cancel
Warranty expiry Monthly List devices whose warranty ends this quarter, plan replacements
Physical inventory count Quarterly Confirm each device is where the register says, by location
Software license true-up Quarterly Compare seats paid with seats used, release the idle ones
Joiner and leaver reconciliation Monthly Match devices and accounts against the starters and leavers list
Retired asset disposal Quarterly Confirm data wiped, certificate filed, register updated
Annual register review Yearly Owner signs off that their category is complete

Each check is one ticket per cycle, with an owner and a due date. The ticket links to the saved filter and holds the outcome as a comment: what was renewed, what was cancelled, what was missing. A year of closed tickets is the evidence an auditor asks for, and the same pattern runs through Jira patch management and Jira vulnerability management.

Three ways to have the checks appear on time #

Remember and create them by hand #

The cheapest way. It works while the same person does it, and it fails the month that person is on leave. A missed quarterly count is usually discovered at the next audit.

Jira Automation #

A Scheduled rule can create a work item on a cron schedule, such as the first Monday of each quarter. It works, and two details matter for this job. Each rule run counts against your plan's automation usage, and quarterly or weekday-position schedules need a cron expression that someone has to get right. The Jira Automation pricing guide covers what a rule spends.

A scheduling app #

Recurring Work Items for Jira is our app, and a calendar of asset checks is the kind of routine it was built for:

  1. Turn the app on for the project that holds the register, and choose who may schedule.
  2. Set the working week and add public holidays, then choose Move it to the next working day under If it falls on a non-working day, so a check that lands on a day off moves rather than appearing when nobody is in: a new rule runs on the day it falls on, holiday or not.
  3. Create one rule per check: every month for renewals, every 3 months for the inventory count, every 12 months for the register review.
  4. Title each with tokens so every cycle is named for its period, for example License true-up {{now.monthName}} {{now.year}}.
  5. Add subtasks for each location or category, the assignee, a label such as asset-check, and a due date as an offset from the run.

It uses no Jira Automation quota, because the scheduling is the app's own. Every run, created, skipped or failed, is written to the rule's history with its reason. A rule only creates tickets in the project it lives in, so the asset team's calendar stays in the asset project. It is free for up to 10 users.

The app creates the tickets. It does not read your Assets objects or scan devices; the register stays wherever you keep it, and the ticket links to it.

Reports worth saving #

Three filters answer most questions about whether the routine is working. Replace ASSETS with your project key.

  1. Did every check happen this year? project = ASSETS AND labels = asset-check AND resolved >= startOfYear() ORDER BY resolved ASC
  2. Which checks are overdue? project = ASSETS AND labels = asset-check AND due < now() AND statusCategory != Done
  3. What renews soon? the 60-day renewal filter above.

Subscribe the owner to the second one weekly. The Jira weekly report guide shows how to turn filters like these into a short summary, and a dashboard can hold all three on one page.

When the manual way is enough #

If one person owns fewer than fifty assets and reviews them in a single sitting each quarter, a calendar reminder and the renewal filter are enough. The recurring tickets earn their place when the checks are shared across people or locations, when renewals arrive throughout the year rather than on one date, or when you need a dated record that every check happened.

For the rest of an IT team's routine, from backups to access reviews, see Jira for IT operations.

Frequently asked questions #

Does Jira have asset management? Jira Service Management includes Assets on its Standard, Premium and Enterprise plans, according to Atlassian's pricing page. Jira Software on its own does not, so teams there often keep the register as a Jira project.

How many assets can I store? Atlassian lists 5,000 objects on Standard, 50,000 on Premium and 500,000 on Enterprise, with more available per object per month.

How do I get a ticket every quarter for the inventory count? With Jira Automation, a Scheduled rule and a cron expression for the first working day of the quarter. With Recurring Work Items for Jira, choose a monthly rule that repeats every 3 months and set the due date a week after the run.

Can I track software licenses in Jira? Yes. Record each license as an asset with its renewal date and seat count, and run a quarterly true-up ticket that compares seats paid with seats used.