Because Assets is already part of the service desk most IT teams use daily, many teams start by tracking hardware in Jira Service Management Asset Management. It is really helpful to associate a laptop with a ticket. But as staff grows, so do the questions: Who has what device, which software licenses aren’t being used, what’s due to be renewed next month, and what does the auditor need to see? From there, many mid-market IT teams wonder whether Jira’s built-in asset management is enough or whether they need dedicated IT asset management (ITAM) software.
The short answer:
If you’re primarily just looking for a simple, ticket-oriented log of your hardware and configuration items, and you’re lucky enough to have a Jira admin who has the time to create and maintain the schema, Jira Service Management’s Assets will do. This is typically not enough if you need software and SaaS license management, automated offboarding, visibility into IT spend, and an audit-ready asset register. The obvious solution for most expanding organizations is to keep using Jira Service Management for tickets and supplement it with an integrated ITAM platform.
This article outlines what Jira Service Management asset management will contain in 2026, situations where it can be used, situations where it cannot, and how various groups of users will experience it, along with making a decision to stay, upgrade or install an alternative ITAM tool.
What Jira Service Management Asset Management Includes
Asset management in Jira Service Management is delivered through Assets, formerly known as Insight. Jira Service Management is now sold as part of Atlassian’s Service Collection, and what you get from Assets depends heavily on your plan.
| Service Collection Plan | List Price (Per Agent, Per Month) | Assets Included? | Included Objects | Notable Asset Features |
| Free | $0 (up to 3 agents) | No | None | None |
| Standard | $21.50 | Yes | 5,000 | Schemas, imports, AQL search, automation |
| Premium | $55.28 | Yes | 50,000 | Adds Data Manager and hardware asset management |
| Enterprise | Custom | Yes | 500,000 | Adds Data Manager and hardware asset management |
Prices are Atlassian’s published list prices as of November 2026. Objects beyond the allowance cost $0.02 per object per month.
Atlassian rolled Assets out to Standard plans in early 2026, so many teams now have it without paying extra. Across paid plans, Assets in the cloud gives you:
- A flexible data model: object schemas, object types, attributes, references and statuses, with starter templates for ITAM, People and Facilities
- Imports: CSV, JSON, Assets Discovery and web address imports, plus cloud imports from AWS, Azure and Google Cloud
- Search and reporting: Assets Query Language (AQL), object graphs and reports through Atlassian’s analytics tools
- Ticket linking: an Assets object’s custom field that attaches assets to Jira work items
- Automation: rules through Atlassian Automation, plus a public REST API
Assets Discovery is Atlassian’s network scanner. It runs on Windows or Linux, logs into any device it discovers on the network, and returns information to Assets. Agentless scans can’t gather information from devices that aren’t on the network when the scans run, so laptops that connect to the office network infrequently require their own Discovery agents.
Data Manager brings pre-existing schemas and scheduled imports to Premium and Enterprise, and the newer hardware asset management experience on Atlassian includes a hardware register, model grouping, stockroom management, and connections between hardware and procurement, repair, and return work. Atlassian’s documentation on that feature doesn’t even cover software licensing.
Where Jira Service Management Assets Works Well
Jira Service Management Assets is a strong choice in a few specific situations, and it’s worth being clear about them before looking at the gaps.
- Context for service desk agents. When an employee raises a ticket, an agent can see the linked laptop, its owner, and its history without leaving Jira.
- Configuration management. Assets works well as a CMDB, mapping services, servers, and dependencies so incidents and changes can be traced to the systems they affect.
- Flexibility. Because you design the schema, Assets can model almost anything, from network gear to office keys.
- Automation inside Jira. Asset data can drive Jira automation rules, such as routing a ticket based on the device’s location.
- No new vendor. On Standard and above, Assets is already included in what you pay for, making it an easy place to start.
If your team mostly needs “which asset is this ticket about?”, Jira Service Management Assets may genuinely be enough.
Where Jira Service Management Falls Short as an ITAM Tool
The limitations show up when asset management becomes a job in its own right, rather than a field on a ticket. These are the gaps IT teams most often run into.
A Blank Canvas You Have to Design Yourself
Jira Service Management Assets is a general-purpose object database. When using Standard, someone needs to decide what types of objects should exist, what attributes they should have, what the relationships are between laptops, people, and locations, and what the statuses correspond to in the asset lifecycle. Starter templates are great for helping to get started, but anything else – a new category of equipment or a new office – has to be done by someone who knows the schema. The “basic add-on” is often a side project if there is no dedicated Jira admin within the team.
Hardware-First, with No Native Software License or SaaS Usage Tracking
If you choose to build software licenses as an object in your assets, it will store them, but it won’t discover SaaS applications from your identity provider, track how often the license is used, or alert on unused seats. As you might have guessed, Atlassian’s hardware asset management focuses on hardware. This often drives pricing differences for many mid-market companies, as software and SaaS are now more expensive than laptops.
Data That Only Stays Fresh If You Keep Feeding It
The asset register is as up-to-date as its last use. Jira Service Management Assets is updated via imports, Discovery scans, cloud imports, Marketplace apps, or custom API work on Standard. Multi-source imports that are scheduled with Data Manager will need Premium or Enterprise. When the MDM, the identity provider, the HR system, and Assets all have their own version of the truth, it’s back to working with spreadsheets for IT teams.
Built for Service Desk Agents, Not Finance, HR or Auditors
Jira Service Management is built around service agents handling tickets. IT teams wanting to know spend per employee, HR teams managing onboarding and offboarding, or security teams needing to know how to prepare for ISO 27001 or SOC 2 are not necessarily Jira users and don’t necessarily want to learn AQL. For these stakeholders, it’s best to be able to see what they need in asset management without sending every question through IT.
Costs That Climb with Plan Tier and Object Count
Switching to Premium for Data Manager and hardware asset management increases the per-agent cost for all service desk agents, not just asset managers. For an illustrative team of 20 agents, Standard costs about $430 per month and Premium about $1,106 per month at list price. The object count grows faster than the device count, since people, locations, models, and contracts can all be counted as objects. If you have an 8,000-object site, and you want an additional 3,000 objects, you would be charged an extra $60 per month, in addition to the agent costs.
How Different Roles Experience Jira Service Management Assets
Whether Jira’s asset management is “good enough” depends on who’s asking. This table compares what each role needs with what Jira Service Management Assets offers on its own and what a dedicated ITAM platform typically adds.
| Role | What They Need | Jira Service Management Assets on Its Own | With a Dedicated ITAM Platform |
| Service desk agent | Device context on tickets | Strong: assets linked to work items | Same, via integration with the service desk |
| IT manager or asset owner | An accurate, current inventory and lifecycle view | Possible, but depends on schema design and import upkeep | Records created and updated automatically from MDM, RMM and identity tools |
| Finance or CFO | IT spend, renewals and cost per employee | Limited; requires custom fields and reporting | Spend reports, renewal timelines and license savings |
| HR or People Ops | Reliable onboarding and offboarding | Manual unless automation is built | HR-triggered joiner and leaver workflows |
| Security or compliance lead | An audit-ready asset register and evidence trail | Possible with significant configuration | Information asset register, risk detection and audit checklists |
The pattern is consistent: Jira Service Management Assets serves the service desk well, while the roles around it are where a dedicated ITAM tool earns its place.
A Quick Decision Guide: Stay, Upgrade or Add an ITAM Tool
Work through these questions in order. The first “yes” usually points to the right option.
- Do you only need to see which asset a ticket relates to? If yes, Jira Service Management Assets on Standard is probably enough. Use the ITAM template and keep the schema simple.
- Do you need to track software licenses, SaaS usage or renewals? If yes, add a dedicated ITAM platform. Upgrading to Premium won’t close this gap, because Atlassian’s hardware asset management focuses on hardware.
- Do leavers regularly keep devices or licenses longer than they should? If yes, look for an ITAM tool that connects to your HR system, so offboarding starts automatically and lists everything to recover.
- Is an audit (ISO 27001, SOC 2, Cyber Essentials) on the horizon? If yes, prioritize a tool with a built-in information asset register and evidence trail rather than building one in Jira.
- Is your main problem large-scale infrastructure mapping for incidents and changes? If yes, Jira Service Management Premium with Data Manager is a reasonable upgrade, since CMDB use cases are where Assets is strongest.
- Is there no one with time to own the Jira schema? If yes, a ready-to-use ITAM platform will save more time than it costs.
The Practical Middle Ground: Keep Jira for Tickets, Use Setyl for Assets
Replacing Jira Service Management isn’t necessary to get better asset management. Many IT teams keep Jira for service requests and incidents and add a dedicated ITAM platform that integrates with it, so each tool does the job it was built for.
Setyl is an IT asset and license management platform designed for exactly this setup. Setyl gives IT teams a single source of truth for hardware, software applications and licenses, people, vendors, and IT spend, and it integrates with Jira Service Management rather than trying to replace it.
How Setyl Works Alongside Jira Service Management
Setyl’s integration for Jira Cloud lets teams link Setyl records, including assets, people, and software applications, to Jira issues. The linked issues are then kept as an issue log and audit trail inside Setyl, so a device’s repair history or an employee’s access requests sit next to the asset record. The integration app is free for Setyl customers.
What Setyl Adds That Jira Service Management Assets Doesn’t
- Automatic records from 100+ integrations. Setyl syncs devices, people, and applications from tools such as Microsoft Intune, Jamf, Kandji (Iru), NinjaOne, Okta, Google Workspace, CrowdStrike, and Cisco Meraki, creating, merging, and enriching asset records without manual imports.
- Software and SaaS license management. Setyl detects applications and logins through SSO and identity providers, tracks license usage, flags inactive and unused licenses, and keeps a timeline of upcoming renewals so notice windows aren’t missed.
- Offboarding tied to HR data. Integrations with BambooHR, HiBob, and Workday trigger onboarding and offboarding, and each employee record shows every asset, license, and admin role to assign or recover.
- Spend visibility for Finance. Spend reports, cost-per-employee reports and replacement planning give Finance answers without a Jira login.
- Audit readiness. An information asset register, risk detection, vendor due diligence, activity logs, and a security audit checklist mapped to ISO 27001 and SOC 2 help teams prepare for audits. Teamwork, the project management software company, uses Setyl to demonstrate its controls during audits and customer due diligence.
- AI access. Setyl’s MCP connector lets teams query and act on Setyl data through Claude, ChatGPT, and other AI assistants.
Setup, Support and Pricing
Setyl can be set up in as little as an hour, a notable contrast to designing an Assets schema from scratch. Setyl won G2’s 2026 Easiest Setup and Best Support awards, holds ratings of 4.8 on G2 and 4.9 on Capterra, and includes unlimited one-on-one support by email, chat, and video. Plans are priced by number of employees rather than by agent or object, start from $300 per month, and include unlimited assets and licenses. Setyl is ISO 27001 certified and GDPR compliant.
Setyl isn’t a service desk and is cloud-only, so it’s designed to complement Jira Service Management, not replace your ticketing.
What a Combined Setup Looks Like Day to Day
Consider a common request: an employee’s laptop screen fails. In a combined setup, the employee raises a ticket in Jira Service Management as usual, and the agent links the device from Setyl to the issue. In Setyl, the IT team sees the laptop’s assignee, purchase date, warranty status, and previous issues in one place, which helps decide whether to repair it under warranty or replace it.
The ticket stays in Jira, where the service desk works. The asset’s full history, including that repair, stays in Setyl, where IT, Finance, and auditors can find it later. Neither team has to maintain a second copy of the other’s data.
Frequently Asked Questions
Does Jira Service Management Include Asset Management?
Yes. Jira Service Management includes asset management through Assets on Standard, Premium, and Enterprise plans. Standard includes 5,000 objects, while Premium adds Data Manager and a hardware asset management experience.
Is Jira Assets Available on the Free Plan?
No. Atlassian’s pricing page lists asset management only on paid Standard, Premium, and Enterprise plans. The Free plan supports up to three agents without Assets.
Can Jira Service Management Track Software Licenses?
Only if you model licenses as objects in a custom schema and update them yourself. Jira Service Management doesn’t natively discover SaaS applications, measure license usage or flag unused licenses, which is why many teams add a dedicated ITAM tool for software.
Do I Need Jira Service Management Premium for Asset Management?
Not necessarily. Standard covers basic, ticket-linked asset tracking, while Premium adds Data Manager, hardware asset management, and a 50,000-object allowance at a higher per-agent price. If your main gaps are software licenses, offboarding, or spend, a dedicated ITAM platform usually addresses them more directly than an upgrade.
Can I Use a Dedicated ITAM Tool Alongside Jira Service Management?
Yes, and it’s a common setup. Platforms such as Setyl integrate with Jira Service Management, so agents can link assets, people, and software to issues, while the ITAM tool automatically keeps the full asset and license record up to date.
