Skip to main content

What JSM LaunchPad does and does not do

launchpad://docs/standard
$launchpad open --docs What JSM LaunchPad does and does not do
Starter·Platform: Jira Service Management Cloud (Assets)·Product Overview·Reading time: ~8 min·Version 1.1·Mar 2026

What JSM LaunchPad does and does not do

JSM LaunchPad installs a working service structure inside Jira Service Management so that requests can route correctly, ownership is defined, and reporting works from day one. It does not attempt to run your service desk for you. It gives you the foundation that everything else connects to.

What LaunchPad does​

1. Installs a working service structure​

LaunchPad creates a complete, ready-to-use structure in Assets: services, supporting systems, ownership mapping, relationships between them, and consistent attribute definitions across every object type. You are not starting from a blank page. The Install Service Model wizard walks you through four steps (Choose, Configure, Install, Complete) and deploys a full CMDB schema template, including object types, attributes, reference types, and optionally sample data. You control the schema name, whether cross-schema references are included, whether custom reference types are created, and whether sample data is loaded.

Deployed Enterprise IT CMDB schema in Assets showing 21 object types with attributes

2. Gives you a production-ready starting point​

The structure LaunchPad creates is designed so you can link requests to services, assign ownership, and report on performance immediately. This removes the typical "design paralysis" phase where teams spend weeks debating object type names, attribute conventions, and relationship hierarchies before writing a single record. With LaunchPad, those decisions are already made for you. You can always refine later, but you start with something that works now.

3. Provides proven models you can reuse​

LaunchPad includes structured templates that reflect real operating environments: a standard service model, cloud infrastructure, service catalogue, vendor and software tracking, cybersecurity, workforce management, and more. These are not abstract reference architectures. They contain the object types, attributes, and relationships that teams actually need when running services in production.

Install Service Model wizard showing the template gallery with category tabs and complexity badges

4. Enables fast setup, not slow design​

Without LaunchPad, teams debate structure for weeks. Naming becomes inconsistent. Ownership is unclear. Different spaces end up with different conventions, and nobody can report across them reliably. With LaunchPad, the structure is already in place. You move straight to using it.

5. Supports capabilities beyond installation​

LaunchPad is not only about installing structure. It also provides:

  • Import and Export: export an existing Assets schema to LaunchPad interchange JSON, or import a JSON file to create a new schema. This gives you portability between environments, with drag-and-drop upload, file validation, and batched import with progress tracking.

Export tab showing schema selector and exported JSON file with Copy and Download options

Import tab with drag-and-drop upload area and example file options

  • Environment Analysis (Pro): scans your Jira instance (spaces, service desks, custom fields) and recommends which LaunchPad templates to deploy. Recommendations are based on keyword matching and signal scoring, with confidence levels (high, medium, low) and evidence drill-down.

Environment Analysis scanner ready to analyse your Jira configuration

  • Request Flow Analysis (Pro): scans a specific service desk space to find fields that could be converted to Assets pickers. Shows enrichment opportunities categorised as "ready to configure" or "unlockable", and can create Assets custom fields directly from recommendations.

Request Flow Analysis showing request types with enrichment opportunities and unlockable fields

Field Analysis tab showing enrichment candidates that could become Assets pickers

  • Installed Service Models: browse all existing Assets schemas in your workspace. Inspect object types, attributes, and reference types, including a relationship graph visualisation.

Schema graph showing all object types and their relationships for the Enterprise IT CMDB

  • Activity Stream: logs recent user actions on the home screen. This is event logging of recent activity, not an audit feature.

Each of these is covered in its own guide. This page focuses on the boundaries of what LaunchPad does and does not do, not on deep functionality.

What LaunchPad does not do​

1. It does not bring in your data​

LaunchPad creates structure only. It does not import servers, users, applications, devices, or CMDB exports from other tools. You connect or import your own data after installation, either manually, through integrations, or using the Assets import features built into Jira.

2. It does not configure how your service desk behaves​

LaunchPad does not build workflows, define SLAs, configure approval chains, or create request types. These are operational decisions that depend on how your organisation runs its services. LaunchPad creates the data model that those operational elements connect to, but the configuration itself is yours to define.

3. It does not replace service management practices​

LaunchPad does not run incident management, change management, or service ownership governance for you. It enables these practices by giving you a consistent structure to work from. Think of it as the foundation, not the building.

4. It does not change existing spaces​

Your Jira spaces remain completely untouched after installation. LaunchPad creates structure in Assets only. You connect spaces to those structures when you are ready, on your own terms.

5. It does not overwrite existing structures​

LaunchPad is additive. It creates new structures, does not modify existing ones, and does not overwrite data. You can safely install it in live environments without risk to what is already there.

What this means in practice​

After installation, you will not have a fully configured service desk. You will have a clear structure, defined ownership, and a reliable foundation to build on. From there: create or connect a service space, link requests to services, test real scenarios, and refine gradually.

When LaunchPad is most useful​

LaunchPad delivers the most value when you are starting Jira Service Management from scratch, introducing Assets for the first time, replacing spreadsheets or fragmented tracking with a proper service model, or standardising service data across multiple teams.

When you may not need it​

If you already have a mature, stable structure in Assets, or heavily customised ownership models that work well, LaunchPad may not be necessary as a deployment tool. Even then, it can serve as a reference model or a validation baseline to compare your existing design against.

Install a structure. Use it immediately. Understand what has been created before you start changing it. Do not begin by redesigning the schema to match a theoretical ideal. Most failures happen when teams customise too early, before they have spent enough time working with the structure as delivered.

The key takeaway​

LaunchPad does not run your service desk. It installs the structure your service desk depends on. Structure first. Then operation. Then optimisation.