Optimisation and automation

Getting a schema deployed and populated is one thing. Getting it to work for you without constant manual effort is another. This section covers the tools and techniques that turn a well-structured CMDB into something that actively supports your service operations: automation rules that keep data current, dashboards that surface the right information at the right time, attribute design that ages well, and a plain-language guide to the pitfalls that catch most teams out.

---

What is in this section?

Dashboards How to build Jira Service Management dashboards that surface meaningful information from your Assets data. Covers the gadgets available, AQL-based filters, the recommended dashboard layouts for different stakeholder groups, and how to keep dashboards relevant as your schema evolves.

Automations Jira Service Management automation rules that work with your deployed schema. Covers the most valuable automation patterns: auto-linking assets to incidents, updating object status on ticket resolution, triggering notifications when SLAs are at risk, and syncing data from external sources.

Common Mistakes to Avoid A candid list of the things that go wrong in Assets deployments, drawn from real implementations. If you read nothing else in this section, read this.

CMDB Maturity Model A four-level progression from "tracking exists" to "operations are driven by the CMDB". No consulting jargon, just the stages teams actually go through and how to move between them.

Continuous Improvement The practical cycle of measuring, identifying, fixing, and verifying data quality over time. Covers what to measure, how often to review, and when you are ready to expand.

---