Jira Query Guide: 7 JQL Examples for Common Tasks in Jira
Need to find Jira issues faster? Explore 7 Jira query examples for overdue tasks, sprints, and team updates. Read now to master JQL.
Jira issues pile up quickly when you need to find one overdue task, check a sprint, or see what your team changed this week. Clicking through filters one screen at a time can turn a simple check into a frustrating detour.
JQL, Jira’s query language, helps you find matching issues with a few clear conditions. But a small syntax mistake or an unfamiliar field can leave you with empty results—or more issues than you expected.
Here’s a practical guide to seven Jira query examples you can adapt for everyday work. You’ll see what each query returns, how to adjust it, and what to check when the results look wrong. Start with a working example, replace the project and values, then refine the conditions to fit your team.
7 JQL Examples for Common Jira Tasks
A Jira query uses JQL conditions to find issues that match specific fields, values, and operators. These seven examples cover common tasks such as finding your open work, checking sprint progress, and locating overdue issues.
Replace ABC with your project key and edit values such as priority, issue type, and release name to match your Jira setup.
1. Find your unresolved issues
assignee = currentUser() AND statusCategory != Done
ORDER BY priority DESC, updated DESC
This returns issues assigned to you that are not in the Done status category. The sort places higher-priority work first, then brings recently updated issues toward the top.
Use assignee = currentUser() when you want the query to work for whoever runs it. To check one colleague’s work, replace it with assignee = jsmith, using that person’s Jira account identifier.
2. Review unfinished work in the active sprint
project = ABC AND sprint in openSprints()
AND statusCategory != Done
ORDER BY rank ASC
This query finds unfinished issues in active sprints for project ABC. Ordering by rank follows the team’s backlog or board order, which can help you review work in its intended sequence.
The openSprints() function depends on Jira’s sprint setup and your access to the relevant issues. If it returns nothing, confirm the project, board, sprint state, and your permissions.
3. Find overdue issues that are still open
due <= endOfDay() AND statusCategory != Done
ORDER BY due ASC
This query finds unfinished issues with a due date of today or earlier. Sorting by due date shows the most overdue work first.
To narrow the results to a project, add project = ABC AND at the beginning. Issues without a due date won’t match this condition, so teams need consistent due-date habits for a useful view.
4. Find unassigned, high-priority work
project = ABC AND assignee is EMPTY
AND priority in (Highest, High)
AND statusCategory != Done
ORDER BY created ASC
This query surfaces open, high-priority issues in project ABC that have no assignee. The oldest issues appear first, helping a lead spot important work that may have been overlooked.
Jira priority names can vary between projects. If your instance uses values such as Critical or Blocker, substitute those exact options.
5. See issues updated in the past week
project = ABC AND updated >= -7d
ORDER BY updated DESC
This query lists project issues updated within the last seven days, with the most recently changed issues first. It’s useful when you need a quick activity review before a stand-up or project check-in.
To exclude completed work, add AND statusCategory != Done. Jira evaluates relative dates when you run the query, so the results shift over time.
6. Find unresolved bugs in a project
project = ABC AND issuetype = Bug
AND resolution is EMPTY
ORDER BY priority DESC, created ASC
This query returns bugs without a resolution in project ABC. Higher-priority bugs appear first, and older issues appear ahead of newer ones within the same priority.
In some Jira workflows, an issue can have a status that looks complete while its resolution remains empty. Checking the resolution field can help identify workflow configuration or issue-update gaps.
7. Check unresolved work planned for a release
project = ABC AND fixVersion = "4.2"
AND resolution is EMPTY
ORDER BY priority DESC, due ASC
This query finds unresolved issues assigned to release 4.2. Replace the release name with the exact version value used in your project.
If your team tracks planned work with a different field, such as a custom release field, update the query to use that field. Confirm that the version is associated with the project before troubleshooting the syntax.
JQL Basics: Fields, Operators, and Functions
JQL combines field names, operators, and values to describe the issues you want to find. Think of each condition as one question: “Is this issue in project ABC?” or “Is it assigned to me?”
For example, project = ABC checks the project field, while assignee = currentUser() checks who owns the issue. Add conditions with AND when every condition must match, or use OR when either condition is enough.
Use operators to shape your results
= matches a specific value, such as project = ABC.!= excludes a value, such as statusCategory != Done.in matches one of several values, as in priority in (High, Highest).is EMPTY finds issues with no value in a field, such as assignee is EMPTY.>= and <= compare dates or other supported values.
Use parentheses when you combine several AND and OR conditions. For example, project = ABC AND (priority = High OR priority = Highest) keeps both priority choices inside the project condition.
Sort results after narrowing them
ORDER BY controls the order of matching issues. A query such as ORDER BY priority DESC, updated DESC sorts first by priority, then by update time.
ASC means ascending order and DESC means descending order. If the result list is hard to scan, change the sorting before adding more conditions.
How to Adapt a Query to Your Jira Project
Start with the closest example, then change one condition at a time. That makes it easier to tell which edit changed your results.
- Choose the task. Decide whether you need a personal work list, a sprint view, or a release check.
- Replace example values. Change
ABC, issue types, priorities, and version names to values used by your team.
- Run the query. Check whether the results make sense before adding another condition.
- Refine the scope. Add a project, status, assignee, or date condition when the result set is too broad.
- Check the sort order. Use
ORDER BY to put the issues you need to act on first.
For example, if your overdue query shows work from several projects, add project = ABC AND at the start. If it still shows too many issues, add an assignee or priority condition.
Field names and available values can differ across Jira projects. Use Jira’s query editor suggestions to check recognized fields and options, especially when working with custom fields.
Save and Share Useful Jira Filters
Once a query gives you a useful view, save it as a filter so you can return to it without rebuilding the conditions. Give the filter a clear name, such as “ABC overdue open issues,” rather than a vague label like “My query.”
Saved filters can support recurring activities. A team lead might review an unassigned-work filter each morning, while a release coordinator checks unresolved version issues before a launch review.
Sharing depends on Jira permissions and your organization’s settings. Before sending a filter to teammates, confirm they can view its issues and that the name explains what the query includes.
Troubleshoot Empty or Unexpected Query Results
When a query returns nothing, check its scope before rewriting it. A project key typo, an old version name, or a status value that differs from your workflow can exclude every issue.
Check fields and values
Confirm that the field exists and that the value matches Jira’s available options. A project may use a custom priority or status, so the value in an example may not match your configuration.
Check permissions and project scope
Jira only displays issues you’re allowed to view. If a teammate sees different results, check their project access and any restrictions on the relevant issues.
Test conditions one at a time
Temporarily remove a condition to see whether the results return. If they do, add conditions back individually until you identify the one narrowing the search too far.
For example, start with project = ABC, then add the status, assignee, and date conditions one by one. This simple check is often faster than changing the entire query.
Value Proposition
When your Jira queries reveal recurring coordination problems, ONES.com offers a separate project management option through ONES Project, a Jira alternative. ONES.com also includes ONES Wiki for knowledge management; the two products are sold separately.
Core Capabilities
- Workflows that need to match team processes: ONES Project supports Jira-compatible workflows and custom workflows, helping teams shape issue movement around their own approval or delivery steps.
- Project fields that don’t fit the work: Custom fields let teams track the details they need, making it easier to organize and review project issues.
- Repeated status checks: Built-in reporting gives teams project views without requiring every review to begin with a manually assembled query.
- Sprint coordination: Sprint management supports planning and tracking work across iterative delivery cycles.
- Repetitive project actions: Automation can handle supported routine steps, helping teams reduce manual process work.
- Reliance on add-ons: Native project capabilities may reduce the need for multiple plugins, depending on the team’s requirements.
- Deployment restrictions: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployment options for different infrastructure needs.
- Concerns about hosting trade-offs: The self-hosted version has full feature parity with the cloud version, so deployment choice does not require accepting a reduced feature set.
ONES.com has a free option for up to 30 seats. Teams can evaluate ONES Project for project management, or ONES Wiki for knowledge management, as separate products.
Application Scenarios
A software team might use sprint management, custom workflows, and automation to coordinate delivery. Its Jira queries could then focus on finding exceptions, such as unresolved high-priority work, instead of recreating the same status report each week.
An organization with restricted-network requirements could consider an Air-gapped or other self-hosted deployment. Teams that also need a knowledge base can assess ONES Wiki separately from ONES Project.
Common Challenges with Jira Queries
Too many issues appear
Problem: A query matches issues across several projects or includes completed work. Solution: Add a project condition and a status or resolution condition, then rerun the query to check the narrower scope.
No issues appear
Problem: A field value, project key, or version name may not match your Jira setup. Solution: Test the project condition first, then add the remaining conditions one at a time.
The query works for you but not a teammate
Problem: The teammate may have different issue permissions, or the query may use currentUser(), which changes its meaning for each person. Solution: Check access and explain user-specific conditions when sharing the filter.
A saved filter becomes confusing
Problem: A generic filter name makes it difficult to know which project or status conditions it contains. Solution: Use a descriptive title and review the query when the team’s workflow changes.
FAQs About Jira Queries
What is the difference between JQL and a basic Jira search?
Jira’s basic search lets you choose common fields and values through a visual interface. JQL gives you more direct control over conditions, operators, sorting, and supported functions. You can use basic search for a quick lookup, then switch to JQL when you need to combine conditions or reuse a precise filter.
Can I use these Jira query examples in any project?
You can use them as starting points, but you may need to change project keys, field values, and custom fields. Jira configurations vary between teams. For example, a project might use different priority names or a custom release field. Run each query, inspect the results, and adjust values to match your project.
How do I find issues assigned to me in Jira?
Use assignee = currentUser() to find issues assigned to the account running the query. Add a condition such as AND statusCategory != Done if you only want unfinished work. You can also add ORDER BY priority DESC to bring higher-priority issues to the top of the results.
Why does my Jira query return different results for another person?
Jira permissions can limit which issues each person sees. A query that uses currentUser() also returns results for the person who runs it, so assigned issues will differ. Check the query conditions and each person’s project access before assuming the filter itself is broken.
Conclusion
A useful Jira query starts with a clear task: find your open work, check sprint progress, flag overdue issues, or review a release. Use the seven examples as starting points, change one condition at a time, and save the filters you return to regularly.
When a query gives you confusing results, check project scope, field values, permissions, and sort order before rebuilding it. That small troubleshooting routine can turn JQL from a syntax obstacle into a practical way to focus your team’s attention.