Configuration Management Database (CMDB)
Build a CMDB in Jira Service Management Assets
Assets in Jira Service Management supports both IT asset management and configuration management, making it possible to build a CMDB that shows the components your business depends on and the relationships between them.
Atlassian describes Assets as its native asset and configuration management tool for tracking assets and configuration items and linking them to service requests, incidents, problems, changes and workloads.
We help you design the right data model, configure Assets to support your service processes, and make sure the CMDB is practical to maintain, easy to update and useful for reporting, automation and operational decision-making.
What the CMDB helps you manage
Assets and configuration items
Track hardware, software, services, systems and other business-critical objects in one structured model.
Relationships and dependencies
Map how assets, services and infrastructure relate to each other so teams can understand operational impact more clearly.
Process support
Connect objects to incidents, service requests, problems and changes so service management work is based on real context.
Data imports and maintenance
Set up the structure so data can be imported, updated and maintained without unnecessary manual effort.
Automation and extracts
Use the CMDB as a foundation for automation, reporting and operational analysis across the Atlassian environment.
Why build a CMDB in Assets?
Better visibility of critical relationships
A well-structured CMDB helps teams understand how services, applications and infrastructure depend on each other. Atlassian highlights this relationship visibility as one of the main benefits of Assets.
Stronger service management
When assets and configuration items are linked to incidents, problems and changes, support and operations teams can make better decisions faster.
Less manual work
A good CMDB structure makes updates, data imports, exports and automation easier to manage.
Earlier risk detection
A clearer view of dependencies and affected services helps identify vulnerabilities, bottlenecks and operational risks earlier. Atlassian describes the CMDB as an important tool for impact analysis and risk management.
How we implement the CMDB
Analyse the current state
We review your current asset and configuration data, map what already exists and identify what can be reused. This helps reveal both bottlenecks and opportunities before the new structure is designed.
Create the data model
We define the object structure, relationships and use cases that the CMDB needs to support. In Assets, this is typically built through one or more object schemas, which Atlassian describes as the core structure for organising object types and objects.
Implement the structure in Assets
We build the categorised object structure in Assets, import data and connect the objects with Jira Service Management processes such as incidents, requests, changes and problems. Atlassian supports linking assets and configuration items directly to this work.
Automate and connect systems
We automate repetitive actions and connect the necessary systems so the CMDB becomes a working part of your service environment instead of a separate static register. Atlassian also supports connected data and reconciliation through Assets Data Manager in relevant plans.
What we typically deliver
Data model and object structure
A CMDB model with clear object types, attributes and relationships built around your organisation’s needs.
Process connections and permissions
Objects connected to service processes, with permissions set by scheme, category or operational need.
Imports, automation and maintenance logic
Practical ways to keep the CMDB current through imports, integrations and repeatable update flows.
What a CMDB can support
Incident and problem management
Understand which assets, services and dependencies are affected so incidents and recurring issues can be handled with better context.
Change management
Assess what a planned change could affect before it is implemented, using service and asset relationships as the basis. Atlassian specifically notes that services connected with Assets help show what changes and major incidents could affect.
Asset and service visibility
Get a clearer operational view of owned assets, service dependencies and business-critical components in one place.
Build a CMDB that supports real service work
Whether you are starting from scattered inventory data or already have a partial structure in place, we can help you design and implement a CMDB in Assets that supports service management, automation and better decision-making.
Let's get in touch!