Jira JQL Queries: 7 Examples for Everyday Searches in 2026
Need to find Jira issues faster? Explore 7 practical jira jql query examples for open work, overdue tasks, and recent changes. Read now to learn.
Finding the right Jira issue should take seconds. Yet broad boards, inconsistent status names, and unfamiliar search syntax can turn a simple task into a long scroll.
JQL gives you a precise way to narrow those results, whether you need your open work, overdue tasks, or issues changed this week. A small set of reusable searches can make daily triage much faster.
Here are seven practical Jira JQL queries you can adapt today, plus clear guidance on fields, dates, sorting, and common errors. Replace the example project key and values with the ones used in your Jira setup. But here’s the truth: a useful query starts with one clear question, not complicated syntax.
7 Jira JQL queries for everyday searches
Each query below answers a common work question. Copy it into Jira’s advanced search, change the example values, and review the results before saving it as a filter.

1. Find your unfinished work
assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC
This search shows issues assigned to you that Jira does not consider complete. The newest activity appears first, making it handy when you return to work after a break.
currentUser() automatically matches the signed-in Jira account. If you need to inspect another person’s work and have permission, replace it with a username or account identifier accepted by your Jira version.
2. See issues created this month
project = ABC AND created >= startOfMonth() ORDER BY created DESC
Replace ABC with your project key. This search returns issues created since the beginning of the current month, with the most recent entries at the top.
For a weekly view, try startOfWeek(). Jira’s date functions use the instance’s calendar and settings, so check the date range in the results if your team starts its week on a particular day.
3. Prioritize high-impact unfinished issues
project = ABC AND priority in (High, Highest) AND statusCategory != Done ORDER BY priority DESC, created ASC
This query narrows a project to unfinished issues with either of two priority values. It sorts higher priorities first, then places older issues ahead of newer ones within the same priority.
Priority names vary between Jira setups. If your team uses values such as Critical or Blocker, use the exact values shown in your issue fields.
4. Find your upcoming and overdue work
assignee = currentUser() AND due <= endOfWeek() AND due IS NOT EMPTY AND statusCategory != Done ORDER BY due ASC
This search gathers your unfinished issues due by the end of the current week. Sorting by due date puts the most urgent deadlines first.
Adding due IS NOT EMPTY makes the intent explicit and avoids relying on how your Jira setup handles issues without a due date. To look further ahead, replace endOfWeek() with a date function that suits your planning window.
5. Review issues moved into progress this week
project = ABC AND status CHANGED TO "In Progress" DURING (startOfWeek(), endOfWeek()) ORDER BY updated DESC
This query looks for project issues whose status changed to In Progress during the current week. It can help a team review work that recently entered its active queue.
Use the exact status name from your workflow. If your Jira configuration uses a different transition history or date range, adjust the query and confirm that the returned issues match your intended review period.
6. Find urgent issues marked with a label
project = ABC AND labels = urgent ORDER BY updated DESC
Use this when your team applies the urgent label to issues needing attention. The results show recently updated matching issues first.
Labels are often typed manually, so spelling and capitalization habits can affect what you find. If your team has multiple labels for the same kind of work, search for each intended value or agree on one label convention.
7. Spot unresolved issues that have gone quiet
project = ABC AND resolution IS EMPTY AND updated <= -7d ORDER BY updated ASC
This search highlights issues with no recorded resolution that have not been updated recently. Older activity appears first, giving you a practical starting point for a backlog review.
An empty resolution does not always mean an issue is actively being worked on. Check its status and team process before taking action; a stale issue may need a new owner, a status change, or closure.
How to read a JQL search
A JQL query usually combines a field, an operator, and a value. In project = ABC, for example, project is the field, = is the operator, and ABC is the value.
You can add conditions with AND when every condition must match, or with OR when either condition is enough. Parentheses make mixed logic easier to understand.
Here’s why: a query is easier to troubleshoot when you build it one condition at a time. Start with project = ABC, inspect the results, then add an assignee, status, or date condition.
Fields and operators shape the results
Common fields include project, assignee, status, priority, created, and updated. Your Jira setup may also include custom fields with names specific to your team.
Use = for an exact match, != to exclude a value, and IN to match one of several values. For empty fields, use IS EMPTY or IS NOT EMPTY.
Functions and sorting add useful context
Functions such as currentUser(), startOfMonth(), and endOfWeek() make searches adapt to the person signed in or the current date. That can save you from updating a filter each Monday.
ORDER BY controls the result sequence. For example, ORDER BY due ASC puts the earliest due dates first, while ORDER BY updated DESC puts the most recently changed issues first.
Build a query that answers one question
Before typing JQL, state what you need in plain English. “Show my open high-priority issues due this week” gives you a clear target: assignee, status, priority, and due date.
Then add one condition at a time and check the results. If the first condition returns 80 issues and adding a priority condition returns 12, you can see exactly how that condition changed the search.
Let me explain: overly broad queries can bury the issues you care about, while overly narrow queries can hide relevant work. A quick review of a few returned issues helps you catch either problem.
Use Jira’s search interface to verify syntax
Jira’s advanced search can flag syntax problems and display matching issues. When you are unsure of a field name or value, use the search interface to explore available choices before adding more conditions.
For instance, a team may call a status Ready for Review rather than In Review. Matching the actual workflow value matters more than guessing what the label should be.
Keep date ranges and time zones in mind
Relative functions can make filters reusable, but a week boundary may differ from your personal expectation. Check the results around Sunday or Monday if a weekly query looks incomplete.
For a fixed reporting window, use explicit dates in the format accepted by your Jira instance. For a recurring search, a relative function is often easier to maintain.
Save and maintain searches you use often
When a query gives you the right results, save it as a filter with a name that explains its purpose. “My open issues due this week” is easier to recognize than “weekly filter.”
You can revisit a saved filter without rebuilding its conditions. If teammates need the same view, check the filter’s sharing permissions and make sure the intended audience can access it.
The best part? A saved filter can support a recurring routine, such as reviewing overdue work every morning. Revisit it when your workflow, project key, or team conventions change.
Make filter names and ownership clear
Use a short name that describes both the audience and the task, such as QA – Unresolved defects. If several people maintain filters, agree on an owner who can update outdated conditions.
Before sharing, confirm that the filter contains no unintended personal or project-specific conditions. A filter designed around one person’s account may not work as a shared team view.
Troubleshoot missing or unexpected results
If a query returns nothing, check the project key, field value, and permissions first. A valid search can still show no issues when you lack access to the relevant project or issue.
If too many issues appear, add one condition that clearly narrows the search, then inspect the result count again. If results seem inconsistent, check status names, custom field values, and date boundaries.
You might be wondering: should you rewrite the whole query when something looks wrong? Usually, no. Remove or test one condition at a time so you can identify which part changes the results.
ONES.com solution for teams managing projects and knowledge
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so teams can choose the capabilities that suit their needs.

For teams reviewing Jira workflows, ONES Project is a Jira alternative with Jira-compatible workflows, reporting, custom fields, sprint management, and automation. It can be useful to evaluate when you want fewer add-on plugins or need a self-hosted deployment.
Core capabilities
- Disconnected project and knowledge workflows: ONES.com combines project management and knowledge management capabilities, helping teams keep planning and team knowledge within a unified platform.
- Jira workflow familiarity: Jira-compatible workflows can reduce the adjustment required when a team evaluates another project management platform.
- Plugin sprawl: Built-in reporting and automation can reduce reliance on separate plugins for common project needs.
- Rigid issue tracking: Custom workflows and fields let teams shape issue tracking around their actual processes.
- Sprint planning needs: Sprint management supports teams organizing and reviewing iterative project work.
- Deployment constraints: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment to match your operating environment.
- Feature differences across hosting models: ONES.com provides full feature parity between cloud and self-hosted versions, so deployment choice does not mean giving up platform features.
- Small-team evaluation: The free plan supports up to 30 seats, giving a small team room to assess the platform.
- AI-assisted work: ONES Assistant brings AI capabilities into the ONES.com platform for teams that want AI support alongside project and knowledge management.
Where teams might apply it
A product team could use ONES Project to manage sprint planning, automate recurring transitions, and review built-in project reports. ONES Wiki can support team knowledge needs when the team also wants a knowledge management product.
A company operating in a restricted network could evaluate an Air-gapped or On-Premise deployment. A distributed organization could compare Cloud and Private Cloud against its operational requirements.
ONES.com is worth considering when project workflows, deployment control, and knowledge management all matter to the evaluation. Teams should verify that their required fields, workflow rules, and reporting needs fit the selected setup.
Common JQL challenges and practical fixes
A query returns no issues
Problem: A search appears valid but produces an empty result set. Fix: Confirm the project key, exact field values, and your access permissions. Remove conditions one by one to find which restriction excludes the issues.
A status condition misses expected work
Problem: Your query uses a familiar status name, but Jira uses a different label or status category. Fix: Check the exact workflow status and decide whether you need one status value or a broader category such as unfinished work.
A date filter changes at an unexpected time
Problem: A relative date search includes or excludes issues near a week or month boundary. Fix: Review the Jira instance’s calendar and time settings, then test the returned dates. Use explicit dates for fixed reporting periods.
A saved filter works for you but not a teammate
Problem: Another person sees different results or cannot open the filter. Fix: Review sharing permissions and remove conditions tied specifically to your account when the team needs a shared view.
Frequently asked questions
What does JQL mean in Jira?
JQL means Jira Query Language. It lets you search Jira issues by fields such as project, assignee, status, priority, and dates. You combine conditions with operators such as =, IN, and IS EMPTY, then optionally sort results with ORDER BY. You can use it for a one-time search or save a useful query as a filter.
How do I search for issues assigned to me?
Use assignee = currentUser() to find issues assigned to the signed-in account. Add a condition such as AND statusCategory != Done to exclude completed work. You can also sort the results with ORDER BY updated DESC to see recently changed issues first. Check your Jira access if expected issues do not appear.
Can I use JQL to search by date?
Yes. You can compare date fields such as created, updated, or due with explicit dates or supported date functions. For example, created >= startOfMonth() finds issues created since the current month began. Relative functions are convenient for recurring searches, while explicit dates suit fixed review periods.
Why does my JQL query return unexpected results?
Common causes include a misspelled project key, a status value that differs from your workflow, a condition that is too broad, or access restrictions. Date boundaries can also affect results near the start or end of a period. Test the query by removing or adding one condition at a time, then compare a few matching issues with your intended search.
Conclusion
Everyday JQL searches become easier when you begin with a specific question, build the query in small steps, and verify the results. The seven examples cover personal work, dates, priority, labels, status changes, and aging issues.
When Jira searches feel slow or confusing, a clear query and a well-maintained saved filter can bring the right issues into view. Start with one search you repeat often, adjust it to your workflow, and share it only with the people who need it.