Jira Asset Management and CMDB: Turning Asset Data Into Something Your Team Actually Uses

Asset Data Is the Foundation of Asset Management

Asset management sounds straightforward - until you try to define exactly what counts as an asset.

What type of IT devices are important for us to track and manage?

Ask most teams what asset management covers, and they'll say devices - laptops, servers, monitors. But it's only part of the picture.

A modern IT environment also includes software licenses, cloud subscriptions, internal applications, and even API integrations that connect one system to another. If it costs money, has an owner, or something else depends on it - it's an asset worth tracking.

For a finance manager, this might mean knowing exactly how many software licenses the company is paying for. For an IT manager, it might mean knowing which server a critical application runs on. For an HR lead, it might mean knowing which laptop and accounts belong to which employee. Different roles care about different assets.

Not long ago, most companies handled it this way: a laptop assigned during a hallway conversation, a license renewal tracked in someone's inbox, a spreadsheet updated whenever someone remembered to. It worked until the person who remembered left the company, or the spreadsheet fell three months out of date. Bringing this process under one structured system isn't just more organized. It's the difference between information that exists and information your team can actually rely on.

What do we need to understand about our IT devices to track them effectively?

Knowing an asset exists isn't enough. To actually manage it, your team needs to know three things: who owns it, what it's connected to, and what condition it's in.

This is what turns a simple list into usable data - jira asset management captures exactly this: ownership, relationships, and status, in one structured record instead of scattered notes.

Why CMDB Is the Part That Makes the Data Useful

What Is Jira CMDB?

Let's dissect the term "Jira CMDB" and look closely at each part.

The concept of a CMDB itself is simple. CMDB stands for Configuration Management Database - it's a specialized database that plays a pivotal role in storing comprehensive information about an organization's IT assets and the intricate relationships between them. That's the core of a cmdb definition - a record of what you have and how it all connects.

How this actually works inside Jira is where it gets more interesting. In Jira, a CMDB isn't a separate product bolted on from outside - it's built into Jira Service Management through the Assets feature (formerly known as Insight), the same platform your team already uses for tickets, workflows, and service requests. This is sometimes referred to as jira service management asset management. It's what people mean when they search for itsm cmdb: a configuration management database designed specifically for IT service management, not a generic inventory list.

That's what "Jira CMDB" really means in practice - an atlassian asset management solution and a cmdb database, unified inside jira asset management.

From Asset List to Dependency Map

Not every team organizes its assets the same way. Jira's Assets feature lets each team organize things their own way. Data can be grouped into logical object schemas based on how it's actually used and who's responsible for keeping it current. An IT team might structure hardware and licenses one way, while a facilities team tracks equipment differently. Jira still lets you create links between objects across these different schemas, turning basic jira asset inventory into a connected map rather than isolated lists. Pre-built templates are available for common use cases like IT Asset Management, People, and Facilities. This means teams don't have to design the structure from scratch.

Just as important as how data is organized is who can see and change it. Assets jira permissions work on two levels:

• Object schema permissions - control who has administrative rights over a particular schema, who can update its data, and who can only view it.
• Object type permissions - useful when Jira Service Management customers should see only certain information within a schema, without being granted access to everything it contains.

Getting this structure right takes a few things: schemas that make sense for your teams, permissions that protect the right data, reliable asset tracking from day one. This is what Softgile's Atlassian Asset Management service handles for clients: configuring schemas, permissions, and templates around how your organization actually works, not a generic default.

The Cost of Keeping CMDB Separate

Some teams still run a separate CMDB tool alongside Jira - often because it was already in place before Jira Service Management was adopted, or because a specific tool was the standard when the process was first set up. Teams keep using a separate tool not because it's cheaper, but simply out of habit. In reality, this is what it actually costs:

• Double data entry - the same asset gets recorded in two systems, doubling the chance of one falling out of date
• Sync gaps - updates made in one tool don't automatically reflect in the other, creating blind spots exactly when accuracy matters most
• Extra integration to maintain - connecting a separate CMDB to Jira means another API, another point of failure, another thing IT has to monitor
• Context switching for your team - support agents jump between systems mid-incident instead of seeing asset and ticket data in one place
• Additional licensing cost - a standalone CMDB tool is a separate subscription on top of what you're already paying for Jira

CMDB vs. Standalone Tools Like ServiceNow

When people search for a configuration management database, many land on ServiceNow by default - it's one of the most recognized standalone platforms built specifically around CMDB functionality. And it's a solid tool on its own. But "standalone" is the operative word: a servicenow configuration management database lives outside your existing service desk, which means every asset record, every dependency link, and every update has to be maintained in a system separate from where your team actually manages tickets, incidents, and requests.

For teams already running Jira Service Management, that separation doesn't add capability - it adds overhead. The same CMDB functionality that ServiceNow offers as a dedicated product is already built into Jira through Assets. There's no second login, no second data model to keep in sync, and no extra integration layer standing between your asset data and the tickets that depend on it. The question isn't whether ServiceNow's approach to a configuration management database works. It's whether your team needs a second system to get the same outcome Jira already provides natively.

Why IT Asset Management Actually Matters

Money lost on assets nobody can find. Ghost assets - equipment that's lost, retired, or no longer in use but still sitting on the books - typically make up 12-25% of fixed asset records in most organizations. Companies keep paying support contracts, insurance, and depreciation on hardware that's long gone. Industry estimates put the total waste at up to 25% of IT budgets.

Software licenses draining budget quietly. Without reliable asset tracking, licenses pile up unused. Recent research puts unused enterprise software licenses at 43%. And when a vendor audit finds the gap, it's expensive: 64% of audited companies paid additional compliance fees, and 35% paid significantly more.

Safer changes. Every update carries some change management risk - but that risk is far higher when nobody knows what a change might break. Visible dependencies mean your team can see the downstream impact of a change before deploying it, not after.

A real security gap. Unknown or unmanaged assets aren't just an efficiency problem - they're a security one. 38% of successful cyberattacks originate from unknown or unmanaged assets. An asset nobody's tracking is an asset nobody's patching.

Better decisions at the leadership level. Beyond day-to-day operations, structured asset data gives IT directors and leadership a clear view of what's actually deployed.

What Determines the Cost of Jira Asset Management

The main point: Asset Management (the CMDB functionality) isn't sold as a separate product - it comes bundled with Jira Service Management's Premium and Enterprise plans, as part of what Atlassian now calls the Service Collection. If your team is already on one of these plans, the CMDB capability is already included. What typically costs extra is the work of setting it up properly, not a separate license.

The exact price for your organization depends on your infrastructure's size and which Jira plan you're already using - the number of agents, how many asset objects you need to track, and whether custom schemas or automations are required. If your setup needs custom-configured schemas or automation rules built around how your team actually works, that's exactly where Softgile's Atlassian Asset Management service comes in.

For the most current, official pricing details, Atlassian's own resources are the most reliable source:

• Atlassian Service Collection Pricing - official plans and current rates
• Jira Service Management Pricing & Packaging Updates — details on Assets object limits and consumption-based pricing

‍