Most PMs can click Jira filters. Fewer can answer hard questions in 30 seconds with JQL. Here's how I'd use Jira Query Language as a product manager—without turning into a full-time reporting analyst.
What JQL is (quick)
JQL is Jira's query language—think SQL-ish filters for issues. Advanced search beats brittle saved filters when questions change weekly.
Queries I'd keep in a personal cheat sheet
| Need | Example pattern |
|---|---|
| My open work | assignee = currentUser() AND statusCategory != Done |
| Unassigned in flight | assignee is EMPTY AND statusCategory = "In Progress" |
| Bugs in a project | project = MYPROJ AND issuetype = Bug AND statusCategory != Done |
| Recently created bugs | issuetype = Bug AND created >= -14d ORDER BY created DESC |
| Stale in-progress | statusCategory = "In Progress" AND updated <= -14d |
| Sprint spillover risk | sprint in openSprints() AND statusCategory != Done |
| Text search | text ~ "checkout" AND project = MYPROJ |
| Exec-watched labels | labels = exec-visibility AND statusCategory != Done |
Syntax varies slightly by Jira Cloud vs Server and your field names—treat these as patterns, then adapt.
How I'd weave JQL into the PM week
- Monday — open sprint unfinished + blocked items
- Midweek — bug inflow vs resolution for the last 14 days
- Planning — unestimated work in the candidate backlog
- Stakeholder asks — label- or component-based slices instead of manual spreadsheets
- Retro inputs — issues that bounced statuses or aged too long
Habits that keep you honest
- Save useful queries as filters; name them like verbs (
bugs-aging,unassigned-wip) - Prefer
currentUser()and relative dates (-7d) so filters travel with you - Don't weaponize JQL for individual surveillance—use it for system health
- If you're querying heroically every day, you may have a workflow design problem
My take
JQL is a PM leverage tool: faster questions, cleaner conversations, less spreadsheet archaeology. Pair tooling fluency with real product craft via the PM Certification and the newsletter.