We Built a JQL Game: Save the Rocket Before the Countdown Hits Zero

[#1]

Reading JQL docs is fine. Writing JQL while a countdown ticks down and a panicked QA engineer named Greg tells you the rocket is wobbling on the pad — that sticks.

So we built it. Launch Trainer is a free, five-level browser game that teaches JQL by giving you a problem you actually want to solve: there is a software bug somewhere on a Mars-bound rocket, you have five minutes, and the only way to find it is to write the right query.

Play Launch Trainer -> No sign-up, no install, runs in your browser.

The Setup

T-5:00. Greg from QA interrupts with the worst sentence in software: "I think there's a software issue somewhere on the rocket?" The MARS project has hundreds of issues across three programs. Mission control is on the line. The clock does not stop.

On the right side of the screen is a Jira-style issue list with a real JQL input labelled ARGON_JQL_SEARCH.EXE. On the left, a pixel rocket on the pad. Below, Greg types out hints in real time. Your job is to narrow hundreds of issues down to one before the countdown hits zero.

What You Learn (in Five Levels)

1. T-5:00 — Where do I even look? Filter by project. The starting view shows issues from MARS, VENUS, and JUPITER all mixed together — you have to scope down before anything else makes sense.
2. T-4:00 — Just the bugs. Combine clauses with AND and add an issuetype = Bug filter. The first taste of stacking constraints.
3. T-3:00 — Critical only. Two priorities matter: Highest and High. Instead of two ORs, you learn the IN (...) operator.
4. T-2:00 — Which component? Mission control radios in: the rocket is wobbling. That's propulsion. You add component = propulsion and find a single suspect: MARS-417, "engine fuel mix off-by-one." But it's In Review. Is the fix actually deployed?
5. T-1:00 — Find the real problem. Native JQL can't filter on time-in-status. JQL Argon can. You write issue in timeInStatus("project = MARS AND component = propulsion", "In Review", "3d") and discover MARS-417 has been sitting in review for eight days. Nobody merged it. You ping the deploy team. Liftoff.

Why a Game?

JQL is a language. Languages don't get learned by reading reference tables — they get learned by using them to say something you actually need to say. The Launch Trainer replaces "here are the operators" with "you have a problem, the syntax is the tool, go."

It's also short. The whole game is five minutes if you know what you're doing, maybe ten if you're learning. We were stricter with ourselves than we usually are: every level had to teach exactly one new concept and immediately make you use it. No scaffolding for its own sake.

And the last level is the point of the whole thing. The first four levels can be solved with native Jira JQL. The fifth one can't — not without JQL Argon JQL ARGON . That's not an accident. The reason we built Argon is that real planning questions ("how long has this been stuck in review?", "which epics have blocked children?", "who commented on this last quarter?") fall outside what stock JQL can express. The game makes that gap visible by handing you a problem that requires you to cross it.

For Teams

If you onboard new Jira admins, project managers, or developers, the trainer is a ten-minute exercise that gets them past the "I've heard of JQL" stage and into "I can write a query." Drop the link in your onboarding doc. It runs in any browser, on any device, with no setup.

And if you've been writing JQL for years — play it anyway. The last level might introduce you to a function you didn't know existed.

You can find JQL game on our website.

Wish you good luck!
Greetings
Bartek from Orbiscend OU (JQL Argon app provider)