Jira-native asset and configuration management

For a detailed look at Assets features by plan, see this comparison table.

Yes. Objects in Assets can be linked to Jira issues as long as there’s an active Jira Service Management Premium or Enterprise license in the same instance.

Moving your CMDB into Jira Service Management would:

• Streamline your work by having all ITSM (requests, incidents, changes, & problems) and CMDB information in one tool
• Provide more context between assets & CIs and incidents & changes so that your Dev and Ops teams can get to the root of the issue faster and manage risks for more seamless deployments
• Reduce costs as other CMDB vendors are expensive
• Increase flexibility to store whatever type of inventory, asset, or record - without the constraints or limits to just IT use cases.

Yes, we offer basic discovery functionality to detect assets and CIs connected to your local network and extract detailed info about each asset.

We also offer integrations with leading discovery solutions like Device42 and Lansweeper to find and import devices into Jira Service Management.

Importing data into Assets is a five step process.

1. Prepare your data.
2. Create an import structure (Discovery, CSV, JSON import, external import).
3. Map your data (with auto or manual creation of object types and attributes)
4. Enable your object type mappings
5. Execute the import

Read the detailed instructions for best practices and tips when importing data into Assets.

Assets was formerly known as Insight from Atlassian’s acquisition of Mindville in 2020. These features have now been rebranded and fully integrated into Jira Service Management under Assets.

Anything. Seriously.

• Traditional IT assets like hardware? ✅
• Configuration items? ✅
• People records? ✅
• Fish? If it’s important to you, it’s important to us ✅

Assets is flexible to your needs. Just create the object type and schema right for you and you’ll be on your way.