What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira/JQL Cheat Sheet
Jira

JQL Cheat Sheet: The Jira Queries You'll Actually Use

JQL, Jira Query Language, is how you search Jira precisely. It drives advanced search, saved filters, board filters and most dashboard gadgets. Every query is a field, an operator and a value, joined with AND or OR and sorted with ORDER BY. Copy the examples below and change the names.

The grammar

Clause: field operator value, as in status = "In Progress". Put values with spaces in quotes.

Combine and sort: project = SUP AND assignee = currentUser() ORDER BY priority DESC, created ASC. Use brackets when you mix AND with OR.

Where to type it: open Jira's work item search and switch from basic to JQL. The editor suggests fields, values and functions as you type.

Copy-ready JQL queries

Replace the project key (SUP here) and names with yours.

You want Type this Note
My open work assignee = currentUser() AND statusCategory != Done statusCategory covers every "done" status your workflows have, whatever they're called.
Nobody has picked it up project = SUP AND assignee is EMPTY AND statusCategory = "To Do" Use is EMPTY, not = "".
Created in the last 7 days project = SUP AND created >= "-7d" Relative dates need quotes. Without them the number is read as milliseconds.
Created since yesterday morning created >= startOfDay("-1") startOfWeek(), startOfMonth() and the endOf… functions take the same offsets.
Overdue duedate < now() AND statusCategory != Done Leaves out items with no due date, which is usually what you want.
Untouched for two weeks statusCategory != Done AND updated <= "-14d" ORDER BY updated ASC Oldest first, so the worst cases sit at the top.
In the current sprint sprint in openSprints() AND project = SUP closedSprints() and futureSprints() work the same way.
Anyone on a team assignee in membersOf("support-team") Uses the group name from your Atlassian admin settings.
Was ever in a status status WAS "Blocked" DURING ("2026/10/01", "2026/10/31") History operators work on six fields only. See the pitfalls below.
Reopened after being fixed status CHANGED FROM "Done" TO "In Progress" Good for spotting work that bounced back.
Children of an epic or parent parent = SUP-120 Replaces the older Epic Link field for new filters.
Words anywhere in the text text ~ "refund failed" Searches summary, description, environment, comments and text custom fields.

JQL operators and keywords at a glance

01

Compare

  • = and !=
  • >, >=, <, <= for dates, versions and numbers
  • IN (A, B) and NOT IN (A, B)
02

Empty or not

  • is EMPTY or is null
  • is not EMPTY
  • Not every field supports these. The field reference says which.
03

Text

  • ~ contains, with word stemming: summary ~ win also finds "wins"
  • !~ does not contain
  • "win*" for a wildcard, escaped quotes for an exact phrase
04

History

  • WAS, WAS IN, WAS NOT, WAS NOT IN
  • CHANGED, with FROM and TO
  • Narrow with AFTER, BEFORE, ON, DURING and BY
05

Functions people use most

  • currentUser(), membersOf()
  • openSprints(), closedSprints()
  • now(), startOfDay(), endOfWeek()
  • updatedBy(user, "-7d")
06

Keywords

  • AND, OR, NOT
  • ORDER BY field ASC or DESC
  • EMPTY and NULL

JQL mistakes that quietly hide results

The query runs and returns something, so nothing looks wrong. These are why the count is off.

!= skips empty fields

How you'll know: priority != High leaves out every item with no priority set.

Fix: Add the empties back: (priority != High OR priority is EMPTY).

~ is not an exact match

How you'll know: summary ~ run also returns "running" and "runs", and odd results for short words.

Fix: For an exact phrase, wrap it in escaped quotes: summary ~ "\"full screen\"". Search one field instead of text when you can. It's faster and more precise.

History search on the wrong field

How you'll know: labels WAS urgent throws an error.

Fix: WAS and CHANGED only work on assignee, fix version, priority, reporter, resolution and status. On items with over 10,000 changes, only the most recent are searched.

A status name that differs by project

How you'll know: status = Done misses items that finish as "Closed" or "Resolved" elsewhere.

Fix: Use statusCategory = Done, which groups every finishing status. The same goes for resolution = Unresolved when your workflows set resolutions.

A filter that references another filter by name

How you'll know: A board or a dashboard breaks after someone renames a saved filter.

Fix: Reference it by ID instead: filter = 10432. IDs never change.

Saving a JQL query as a filter, and the new Jira names

Once a query works, save it as a filter from the search screen. You can star it, share it with a team, point a board at it, or use it as the source for a dashboard gadget. A filter subscription emails its results on a schedule, and a scheduled Jira Automation rule can run the same JQL and act on what it finds. For alerts on a filter, those built-in options are usually enough.

Atlassian has been renaming things in Jira Cloud: projects are now spaces and issues are work items in the interface and docs. Your existing queries don't need changing. Atlassian says project keeps working in JQL, and saved filters carry on as before.

If you search through the REST API, the old search endpoint is gone from Jira Cloud. Our Jira API page covers the replacement and how it pages through results.

Questions people ask

What is JQL in Jira?

JQL is short for Jira Query Language. It's Jira's structured search syntax: fields, operators, values and functions, combined with AND, OR and NOT and sorted with ORDER BY. It powers advanced search, saved filters, board filters, Automation conditions and most dashboard gadgets.

How do I search in Jira using JQL?

Open the work item search and switch from basic to JQL. Type a query such as project = SUP AND statusCategory != Done, and Jira suggests field names and values as you go. Press Enter to run it.

Can I save a JQL query in Jira?

Save it as a filter from the search screen after running it. Saved filters can be starred, shared, used by boards and dashboards, and subscribed to, so the results arrive by email on a schedule.

Is JQL the same as SQL?

No. They look alike, but JQL only filters and sorts Jira work items. There's no SELECT, no joins and no grouping, and it has Jira-specific functions like currentUser() and openSprints(). For counts and groupings, use a dashboard gadget or export the results.

How do I find everything assigned to me in JQL?

Use assignee = currentUser() AND statusCategory != Done ORDER BY priority DESC. Because it uses currentUser(), the same saved filter works for everyone it's shared with.

Can JQL search data that lives outside Jira?

It can't. JQL only sees what's stored in Jira. A filter of open support tickets can't also show which customers are behind on an invoice. That takes pulling the filter's results through the API and joining them with the billing system, which is the kind of report n-frames builds.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.