Compare
=and!=>,>=,<,<=for dates, versions and numbersIN (A, B)andNOT IN (A, B)
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.
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.
Replace the project key (SUP here) and names with yours.
assignee = currentUser() AND statusCategory != Done statusCategory covers every "done" status your workflows have, whatever they're called.project = SUP AND assignee is EMPTY AND statusCategory = "To Do" Use is EMPTY, not = "".project = SUP AND created >= "-7d" Relative dates need quotes. Without them the number is read as milliseconds.created >= startOfDay("-1") startOfWeek(), startOfMonth() and the endOf… functions take the same offsets.duedate < now() AND statusCategory != Done Leaves out items with no due date, which is usually what you want.statusCategory != Done AND updated <= "-14d" ORDER BY updated ASC Oldest first, so the worst cases sit at the top.sprint in openSprints() AND project = SUP closedSprints() and futureSprints() work the same way.assignee in membersOf("support-team") Uses the group name from your Atlassian admin settings.status WAS "Blocked" DURING ("2026/10/01", "2026/10/31") History operators work on six fields only. See the pitfalls below.status CHANGED FROM "Done" TO "In Progress" Good for spotting work that bounced back.parent = SUP-120 Replaces the older Epic Link field for new filters.text ~ "refund failed" Searches summary, description, environment, comments and text custom fields.= and !=>, >=, <, <= for dates, versions and numbersIN (A, B) and NOT IN (A, B)is EMPTY or is nullis not EMPTY~ contains, with word stemming: summary ~ win also finds "wins"!~ does not contain"win*" for a wildcard, escaped quotes for an exact phraseWAS, WAS IN, WAS NOT, WAS NOT INCHANGED, with FROM and TOAFTER, BEFORE, ON, DURING and BYcurrentUser(), membersOf()openSprints(), closedSprints()now(), startOfDay(), endOfWeek()updatedBy(user, "-7d")AND, OR, NOTORDER BY field ASC or DESCEMPTY and NULLThe query runs and returns something, so nothing looks wrong. These are why the count is off.
!= skips empty fieldsHow 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 matchHow 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.