Discover
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.
Scan your environment
LaunchPad's Environment Analysis scans your entire Jira instance. Every space, every service desk, every custom field. It reads the names, normalises common synonyms, and filters out test and sandbox noise.
Then it scores what it finds against the available LaunchPad templates.
The result is a set of confidence-rated recommendations. Each one tells you which schema fits your environment, why it thinks so, and which specific spaces, fields, and service desks triggered the match. A typical scan takes three to five seconds.
You're not committing to anything. You're getting a picture.
A finer-grained request flow analysis (scanning a single service space for enrichment opportunities against Assets object types) is scoped on the roadmap for release after Marketplace launch.
What you get
The scanner doesn't change anything. It's read-only. What it gives you is visibility:
- A clear picture of how much structure your Jira instance already has.
- Schema recommendations ranked by confidence, with the evidence behind each one.
- A starting point grounded in your actual environment, not a guess.
Why this matters
The usual approach is to pick a schema 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.
You don't need to start from zero. You start from what already exists.
Where to next
You have scan results. Now pick the template that fits. Choose a service model walks through the decision tree and the comparison guide.