Skip to main content
launchpad://docs/standard
$launchpad open --docs Discover

Discover

Starter·Platform: Jira Service Management Cloud (Assets)·Guide·Reading time: ~4 min·Version 2.12.0·Jun 2026

Discover

Most teams don't start from zero. They start from a mess.

Jira spaces that have been running for years. Service desks with dozens of request types. Custom fields that someone created in 2021 and nobody remembers why. The problem isn't that your organisation has nothing. It's that nobody can see what's already there, or what it adds up to.

Discovery is how you find out. LaunchPad reads what you already have, tells you what it adds up to, and shows you where to improve it. There are two scans, depending on how wide you want to look:

  • Environment Analysis looks across your whole Jira instance and recommends which service model fits.
  • Request Flow Analysis zooms into a single service project and finds where the right fields are missing, then lets you add them.

Neither one asks you to commit to anything before you've seen the picture.

Environment Analysis: scan the whole instance​

Environment Analysis reads across your Jira instance: service desks, projects, custom fields, request types, and the fields on each request type. It tokenises the names, normalises common synonyms (including British and American spellings), and filters out test and sandbox noise.

Then it scores what it finds against all thirteen LaunchPad service models.

The result is a set of confidence-rated recommendations, ranked high, medium, or low. Each one tells you which service model fits your environment, why it thinks so, and which specific projects, fields, and service desks triggered the match. Weaker candidates that a stronger model already covers are folded into a separate suppressed list, so the shortlist stays readable. Where a partner integration fits the picture (for example PIO, Lansweeper, Jamf, AWS Config, or a CSV import), the scan suggests that too.

When you're ready, each recommendation links straight to its service model so you can install it. Until then you're not committing to anything. You're getting a picture.

Environment Analysis stays free in every licence state. The only requirement is that you're a Jira administrator, since the scan needs read access across the instance.

Request Flow Analysis: go deep on one project​

Environment Analysis tells you which model fits. Request Flow Analysis goes the other way: it picks a single service project apart and finds where the right structure is missing.

It reads the project's request types, fields, screens, and queues, then checks them against the Assets schemas you've actually deployed. The interesting part is what it finds without being told. It probes which fields your real issues populate, reads the JQL behind your queues to spot fields that drive routing and SLAs but never appear on a form, and inspects the option values inside select fields to reveal asset relationships the field name never gave away.

The findings come back in three buckets:

  • Ready to configure, where an Assets schema already exists and a field can be linked to it.
  • Needs template, where the right service model isn't deployed yet, with a jump to install it.
  • Enrichment opportunities, the more general suggestions plus duplicate and inconsistent-coverage findings.

Each finding comes with an action. LaunchPad creates the Assets-backed object-picker field for you, gives it a project and issue-type context, and adds it to the relevant request-type screens. Some boundaries are deliberate. It only ever adds a new field; it never replaces or swaps the original one, and it doesn't migrate existing values. Because the Forge API can't set the object filter, LaunchPad hands you a deep link to finish the AQL configuration in Jira. Fields land on Jira screens, not inside ProForma forms.

Request Flow Analysis needs an active LaunchPad licence and Jira admin rights, and the field-creation step is rate limited.

What you get​

Environment Analysis is read-only: it reads your configuration and gives you visibility.

  • A clear picture of how much structure your Jira instance already has.
  • Service model recommendations ranked by confidence, with the evidence behind each one.
  • A starting point grounded in your actual environment, not a guess.

Request Flow Analysis is read-and-act: it finds the gaps in one project and lets you close them, one field at a time, with you in control of every change.

Why this matters​

The usual approach is to pick a service model and hope it fits. Or to spend weeks auditing your Jira instance by hand before making a decision.

Discovery replaces both. It reads your environment in seconds and tells you what you have, what fits, and where to start. And once a model is in place, Request Flow Analysis keeps finding the gaps, so improving your setup is the same kind of guided step as starting it.

You don't need to start from zero. You start from what already exists.

Where to next​

You have scan results. If Environment Analysis pointed you at a model, Choose a service model walks through the decision tree and the comparison guide before you install. If Request Flow Analysis turned up gaps in a project you already run, follow its findings to add the fields it suggests.