Jira Filters: A Practical Guide to Building Better Queries
Struggling to find the right Jira issues? Build better jira filters with simple searches and JQL. Read now to save time and spot blockers.
Jira can hold the exact issue you need, yet finding it can feel like searching through a crowded workshop without labels. A broad search returns noise, while a query that is too narrow can hide work that needs your attention. Repeating the same manual search every morning wastes time and makes it easier to miss a blocker. Jira filters turn search conditions into reusable views of your issues. You can start with simple field selections, then use JQL to combine conditions, sort results, and save a query for later. Here’s the practical path: understand how filters work, build a query that answers one clear question, and share it carefully when others need the same view.
What Jira filters are and how they work
Jira filters are saved searches that show issues matching criteria you choose. You can create one using Jira’s basic search controls or write a query in Jira Query Language (JQL). The results update when you run or refresh the search.
A filter answers a specific question about your work. For example, you might want to see unresolved bugs assigned to you, tasks updated this week, or open issues in one project.
Basic search lets you choose common fields through a point-and-click interface. Advanced search uses JQL, which gives you more control over conditions, operators, and sorting.
Think of a filter as a reusable recipe. Instead of checking the same project and status settings every day, you save the conditions once and return to the matching issues whenever you need them.

Build a useful query, one condition at a time
Start with one practical question. A focused question helps you choose fields that matter and avoid a query that returns hundreds of unrelated issues.
- Open issue search. In Jira, go to issue search or the search area for issues. The exact menu labels can vary by Jira version and configuration.
- Choose basic or advanced search. Use basic search when you want to select common fields visually. Switch to advanced search when you need to write or edit JQL.
- Select a project or issue type. Narrow the results to the work you care about. For example, select a project and limit results to bugs.
- Add conditions for the work state. Choose a status, assignee, priority, or another relevant field. Add only conditions that help answer your question.
- Review the results. Check several issues to confirm the query returns the right work. If it misses an issue, reconsider the field or value you selected.
- Save the search. Give it a clear name, such as “Open bugs assigned to me.” A specific name is easier to recognize than “My filter.”
Here’s why: each additional condition narrows the results. If you add a restriction that does not serve your goal, the filter may hide useful issues.
For example, a support lead may begin with all open issues in a project. Adding “priority is High” can turn that broad view into a daily escalation check.
Use JQL to combine fields and conditions
JQL is Jira’s query language for describing which issues a search should return. A basic query uses a field, an operator, and a value. You can add more conditions with AND or OR.
For example, this query finds unresolved issues in project ABC and sorts the most recently updated issues first:
project = ABC AND statusCategory != Done ORDER BY updated DESC
project and statusCategory are fields. The operator = checks for a matching value, while != excludes one. ORDER BY controls the order of the results.
Common operators include =, !=, IN, NOT IN, IS, and IS NOT. Text fields can also support operators such as ~, depending on the field and Jira configuration.
You might be wondering: how can a query match one of several values? Use IN when a field can match any value in a group. For example:
project = ABC AND priority IN (High, Highest)
Use parentheses when you combine AND and OR. They make the intended logic clear, especially when you want one condition to apply to multiple alternatives.
project = ABC AND (priority = High OR priority = Highest)
Jira’s available fields and supported operators can depend on your configuration and installed apps. If a field name fails, check its exact Jira name before changing the rest of your query.
Refine results with dates, people, and sorting
A query becomes more useful when it reflects how your team works today. Relative dates, ownership, and sorting can help you focus on current tasks without rewriting the search each week.
For example, this query finds issues in project ABC that changed in the past seven days:
project = ABC AND updated >= -7d ORDER BY updated DESC
To show issues assigned to the person running the search, try assignee = currentUser(). This can make one saved filter useful to each team member, provided the other conditions fit everyone’s work.
Sorting changes the order of matching issues, not which issues qualify. If a team lead wants recently changed tasks first, ORDER BY updated DESC puts the newest activity at the top.
Let me explain: filtering and sorting solve different problems. Use conditions to decide what belongs in the results, then use sorting to decide what people see first.
Save, share, and use filters with care
Saving a filter makes a useful query easier to return to. Choose a name that describes its purpose, such as “Unassigned critical issues” or “Sprint 12 carryover.”
Sharing can help a team use the same view, but access settings matter. Check who can view or edit a filter before adding it to a team workflow. Available sharing options can vary with Jira permissions and administration settings.
Saved filters can also support dashboards and other Jira features. For example, a team may display unresolved high-priority issues on a dashboard, then open the filter to inspect individual results.
Be deliberate about ownership. If a filter supports a recurring team process, make sure its owner and permissions will remain appropriate when team responsibilities change.
Value proposition: ONES.com brings project management and knowledge management together on one platform, while ONES Project is a Jira alternative for teams evaluating their project workflows. ONES Project and ONES Wiki are sold separately.

When your team reviews its Jira setup, compare the work you need to support with the capabilities available in each platform. A filter is one part of a broader workflow that can include issue tracking, reporting, planning, and team knowledge.
Core capabilities
- Disconnected project and knowledge work: ONES.com combines project management with knowledge management on one platform, giving teams a shared environment for coordinating work and knowledge.
- Jira workflow requirements: ONES Project offers Jira-compatible workflows, helping teams assess whether their established processes can carry over.
- Limited workflow flexibility: Custom workflows and fields let teams represent their processes and issue details in the platform.
- Manual project oversight: Built-in reporting gives teams reporting capabilities within ONES Project.
- Sprint planning needs: Sprint management supports teams that organize work in iterative development cycles.
- Repetitive routine work: Automation can handle configured actions and reduce manual steps in suitable workflows.
- Plugin-heavy setups: Native capabilities can reduce reliance on plugins for supported workflows, reporting, and project needs.
- Deployment restrictions: ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.
Application scenarios
A software team with a Jira-based sprint process might assess ONES Project’s Jira-compatible workflows, sprint management, custom fields, and reporting. The team can compare its required workflow details before deciding whether a change suits its needs.
An organization with deployment restrictions may evaluate ONES.com’s On-Premise, Private Cloud, or Air-gapped options. Teams can also explore the free plan, which supports up to 30 seats, and determine whether ONES Project, ONES Wiki, or both fit their requirements.
Common challenges when creating Jira filters
The query returns too many issues
Problem: A search with only a project condition may return more work than you can review. Solution: Add a useful condition, such as status, issue type, assignee, or a recent update date. Check that each added condition reflects the question you are asking.
The query returns no issues
Problem: A misspelled field, incorrect value, or overly strict set of conditions can leave the results empty. Solution: Remove one condition at a time and inspect the results after each change. Confirm that field names and values match the options used in your Jira configuration.
OR conditions change the results unexpectedly
Problem: Combining several AND and OR conditions can make a query hard to interpret. Solution: Add parentheses around related alternatives. For example, group high and highest priority together before combining them with a project condition.
Teammates cannot see a shared filter
Problem: A teammate may lack permission to view the filter, even if they can access the project. Solution: Review the filter’s sharing settings and confirm the relevant Jira permissions. Check dashboard access separately if the filter appears there.
Frequently asked questions
What is the difference between a Jira filter and JQL?
JQL is the language you use to describe issue search conditions. A Jira filter is a saved search that can use those conditions. You can create a filter through basic search controls or write its query in advanced JQL. Saving the search lets you return to the same criteria without rebuilding them each time.
Can I use a Jira filter for more than one project?
Yes. A query can include multiple project values when your Jira permissions and setup allow access to them. For example, a JQL query can use project IN (ABC, XYZ) to search across two projects. Add any status or issue-type conditions needed to keep the results relevant.
Why does a saved filter show different results later?
A saved filter runs its search conditions against the issues available when you open or refresh it. New issues may match, existing issues may change, and permissions can affect what you can see. A relative date condition, such as updated >= -7d, also moves forward as time passes.
How do I make a Jira filter useful on a dashboard?
First, save a query that returns the issues your dashboard should highlight. Then add a dashboard gadget that can display a saved filter, and select the relevant filter. Check sharing and dashboard permissions so the intended viewers can see the results. A concise filter name also helps teammates recognize the right view.
Can other people edit a filter I share?
That depends on the sharing permissions you choose and the Jira settings available to you. Some people may be able to view a filter without being able to edit it. Review the filter’s access settings before relying on it for a team process, and check the dashboard separately if you use the filter there.
Conclusion
Jira filters make repeat searches easier by saving conditions for issues you want to review. Start with one clear question, build a focused query, and check real results before saving it. Use JQL when basic search does not provide enough control, and add parentheses when combining alternatives.
But here’s the truth: a saved search only helps when its criteria, name, and sharing settings make sense to the people who need it. Refine the filter as your work changes, and consider how your wider project workflow supports reporting, planning, and collaboration. With a clear query and sensible access, Jira filters can turn a crowded issue list into a practical view of the work ahead.