What is LaunchPad for Jira Service Management?
What is LaunchPad for Jira Service Management?
You have got Jira Service Management. You have got Assets. But between you and a working CMDB sits a wall of decisions: which object types to create, what attributes to track, how everything should connect. Most teams either spend weeks on that design work or, worse, skip it entirely and end up with a flat structure nobody maintains six months later.
LaunchPad for Jira Service Management skips that wall entirely. Pick a template, click deploy, and walk away with a production-ready schema in minutes.
What LaunchPad does
LaunchPad for Jira Service Management is an Atlassian Forge app that deploys pre-built object schemas directly into Assets. Each schema ships with a complete set of object types, attributes, and relationships, designed by people who have built CMDBs in production environments.
You do not design the schema. You deploy it. Then you populate it with your data.
How it works: the short version
| Step | What You Do |
|---|---|
| Install | Get LaunchPad from the Atlassian Marketplace |
| Browse | Open the template gallery and pick a schema |
| Deploy | Click deploy. LaunchPad creates the full schema in your Assets instance |
| Populate | Add your first records using the structure that is now in place |
That is the entire flow for a first deployment. No configuration files, no scripting, no database migrations.
What you get
Every schema includes:
-
Object types with sensible names and pre-defined purposes (for example, Server, Application, Person)
-
Attributes appropriate to each object type, with the right data types already configured
-
Reference types that define how objects relate to each other (for example, a Server "hosts" an Application)
-
A Quick Start Guide with deployment steps, recommended first records, and AQL query examples
-
A Governance Playbook covering ownership, review cadences, and data quality patterns
-
A Forms Specification describing recommended portal forms you can configure for the schema
Who it's for
LaunchPad for Jira Service Management is built for the people who actually have to make Assets work: IT administrators setting up a CMDB for the first time, ITSM consultants deploying standardised structures for clients, service desk managers who need asset tracking but do not have weeks to spend on schema design, and operations teams finally moving off spreadsheets.
If you have been putting off your CMDB because the design work felt overwhelming, this is the on-ramp you were waiting for.
The available schemas
Five production-ready schemas cover the most common starting points for a Jira Service Management CMDB. Every deployment uses the same batched, additive Forge flow.
| Schema | What It Covers |
|---|---|
| Basic CMDB | Person, Server, Application, Location. The simplest starting point |
| Core Schema | The organisational backbone: people, teams, departments, locations, vendors, applications, cost centres |
| Standard CMDB | Comprehensive infrastructure coverage including network, cloud, databases, and licences |
| Service Catalogue | IT service offerings, service levels, support teams, request types, and knowledge articles |
| Priority Matrix | Impact and urgency mapping for incident prioritisation |
Additional schemas (SLA Management, Cloud-Native Infrastructure, Cybersecurity, Software Asset Management, Vendor Management, Workforce Management, Enterprise IT CMDB, Documentation Management) are scoped on the roadmap for release after Marketplace launch.
What LaunchPad does not do
LaunchPad creates the structure. It does not populate it with your data automatically. That part is still yours, though the documentation covers the fastest ways to do it.
For a clear picture of what is in and out of scope, read What LaunchPad Does and Does Not Do.