NetBox Labs has launched general availability of its Jira Service Management Assets Integration, which syncs infrastructure data from the NetBox Labs platform into Jira Assets as native, linked, queryable objects. The first run provisions the full 28-type schema (spanning core NetBox, virtualization, and the netbox-inventory and netbox-lifecycle plugins) automatically, and subsequent runs validate the schema before writing, sync only changed objects by netbox_id, and remove deleted objects after a configurable grace period. The sync is one-directional and scheduled, keeping NetBox as the system of record while Jira gets up-to-date infrastructure context for change approvals, renewal tracking, and blast-radius analysis. It complements an existing certified integration for ServiceNow. Requires an ITSM integration entitlement and a Jira Cloud account with Assets enabled.
Table of contents
What keeps a CMDB trustworthyThe schema builds and validates itselfEvery device, rack, and IP, where the ticket already livesThe NetBox Labs platform stays authoritative, the service desk consumesWhat it looks like in practiceGetting startedQuestions this post answers
What does the NetBox Labs Jira Assets Integration do when it first runs?
It provisions the complete 28-object-type schema in Jira Service Management Assets, including all attributes and references, before any data moves. The types span core NetBox, virtualization, and the netbox-inventory and netbox-lifecycle plugins. Every subsequent run rechecks the target schema before writing, and a check-only mode lets teams gate the sync inside an existing pipeline. Track integration releases like this as infrastructure and ITSM tooling evolves, on daily.dev.
How does the NetBox Labs Jira integration avoid creating duplicate records when a device is renamed?
Objects are matched on netbox_id rather than on name, so renaming a device in NetBox updates its existing Jira Assets record instead of creating a second one. After the initial sync, only changed objects are written, and objects deleted in NetBox are removed from Jira Assets after a configurable grace period so retired hardware does not linger in the record. Engineers wiring up CMDB syncs can compare integration patterns like this on daily.dev.