Jira Quick Filters: A Step-by-Step Guide to Setup and Use
Need a clearer Jira board? Learn how jira quick filters create focused views for tasks, bugs, and releases. Read now to set yours up.
Jira boards get crowded quickly. When every issue appears at once, it can be hard to spot your own work, urgent bugs, or tasks tied to a particular release.
Opening separate boards or changing the main board filter for every question slows your team down. It can also hide useful work from other people who rely on that board.
Jira quick filters offer a simpler way to narrow a board temporarily. You can create a filter with JQL, add it to a board, and switch it on when you need a focused view. But here's the truth: a quick filter is only useful when its query matches a real team need. This guide walks you through setup, practical examples, and troubleshooting so you can make filters your team will actually use.
How to Set Up and Use Jira Quick Filters
A Jira quick filter is a saved JQL condition that you can switch on or off while viewing a board. It narrows the issues shown without changing the board’s main filter.
For example, a team might add a quick filter named “My Open Issues” with the query assignee = currentUser() AND statusCategory != Done. Anyone viewing the board can select it to see their unfinished work.

1. Open the board settings
Go to the Jira board where you want the quick filter to appear. Open the board menu, then choose Board settings or the equivalent settings option in your Jira interface.
You may need board administrator permissions to edit the configuration. If you cannot find the settings, ask the board owner or a Jira administrator to check your access.
2. Find the Quick Filters settings
In board settings, open Quick Filters. You’ll see the filters already configured for that board, if there are any.
Quick filters belong to a specific board. A filter added to one board will not automatically appear on every other board, even when those boards show similar work.
3. Add a clear filter name and JQL query
Select the option to add a quick filter. Enter a short name that tells teammates what they will see, then add a valid JQL query.
For example, a filter named High Priority could use priority = High. A filter named Unassigned Bugs could use issuetype = Bug AND assignee IS EMPTY.
4. Save and test the filter
Save your change, return to the board, and select the new quick filter. Confirm that the displayed issues match the name and query.
Try the filter with a few known issues. If you expected to see an open bug but it disappears, inspect its fields and adjust the JQL before sharing the filter with your team.
5. Combine filters carefully
You can often activate more than one quick filter at a time. Jira then narrows the board to issues that match the active conditions together.
For example, selecting My Open Issues and High Priority may show only your unfinished, high-priority work. Test combinations your team is likely to use, because two individually useful filters can create an empty view when combined.
What Quick Filters Can—and Cannot—Change
A quick filter changes the issues visible on a board for the person viewing it. It does not rewrite the board’s main filter, change issue fields, or move work between columns.
Think of the main board filter as the outer boundary and quick filters as temporary lenses. If the main filter excludes a project or issue type, a quick filter cannot bring those issues into view.
Here's why that distinction matters: if teammates cannot see an issue even when every quick filter is off, check the board’s main filter and permissions first. A quick filter only works with issues already available to the board.
Quick filters are useful for temporary views
A sprint board can show all active work by default, while quick filters let a developer see their own tickets or a product owner focus on defects.
That keeps one shared board useful for different roles. People can change their view without asking an administrator to create a separate board for every question.
Quick filters do not replace board configuration
Board columns, swimlanes, estimation settings, and the main board filter are separate configuration choices. Quick filters sit alongside those settings rather than replacing them.
If a whole category of work should always be excluded, update the board’s main filter instead. If the category should remain available but only needs occasional focus, a quick filter is a better fit.
Useful JQL Examples for Jira Boards
The strongest quick filters answer questions your team asks repeatedly. Start with a simple condition, give it a plain name, and add complexity only when the view needs it.
For example, a support team might switch between urgent requests and unassigned defects. A development team could use filters for personal work, blockers, or issues targeted for a release.
| Filter name | Example JQL | When it helps |
| My Open Issues | assignee = currentUser() AND statusCategory != Done | When each person needs to focus on their unfinished work. |
| High Priority | priority = High | When the team wants to review urgent issues first. |
| Unassigned Bugs | issuetype = Bug AND assignee IS EMPTY | When a triage lead needs to find defects without an owner. |
| Recently Updated | updated >= -7d | When teammates want to spot issues changed in the past week. |
| Current Sprint | sprint in openSprints() | When a board includes work beyond the active sprint. |
JQL field names and available functions can vary with your Jira setup and permissions. Try a query in Jira’s issue search before adding it to a board, then confirm it behaves as expected on that board.
Keep names understandable at a glance
Names such as My Open Issues and Needs Triage tell people what a filter does. Labels like Filter 1 or Query A force teammates to remember what each option means.
If a query has a technical condition, put that detail in the JQL rather than making the visible name difficult to scan. A useful name describes the outcome, not the syntax.
How to Design Quick Filters Your Team Will Use
Before adding a filter, listen for recurring questions: “What is blocked?” “Which bugs are still unassigned?” or “What should I finish this week?” Each repeated question could become a practical board view.
But here's the truth: adding a filter for every possible situation can make the board harder to use. Choose a small set that reflects real decisions, then remove options that no longer help.
Match the filter to a work habit
A filter is most useful when it supports an action. For example, a daily stand-up filter might show work updated recently, while a triage filter could surface unassigned bugs.
Compare “Needs Attention” with a broad filter named “All Issues.” The first points people toward a task; the second may offer little beyond the board’s default view.
Check the fields your query depends on
JQL can only return the expected issues when the relevant fields are maintained. If nobody assigns priority consistently, a filter for high-priority work may miss issues that need attention.
For instance, a release filter using fixVersion = "Version 2.4" depends on the team setting that release field on the right issues. A query cannot compensate for inconsistent issue details.
Review filters as the project changes
Projects evolve. A sprint may close, a release name may change, or the team may stop using a label. Review quick filters when the board changes so stale options do not linger.
A short quarterly review is often enough for a stable team. For an active release, check filters during planning and closeout so their names and results continue to match the work.
Common Quick Filter Problems and Fixes
When a quick filter seems broken, first turn off all active quick filters. Then check the board’s main filter, the issue fields used in your JQL, and your permissions.
Here's why: an empty board can result from an overly narrow query, multiple filters being active, or issues being excluded before the quick filter runs. Checking one condition at a time makes the cause easier to identify.
The filter returns no issues
Confirm that at least one issue matches the query. Check spelling, field values, project scope, and whether a status or priority has a different name in your Jira setup.
For example, a query for priority = High will not find issues marked Highest. Test the query in issue search and compare it with the fields on an issue you expected to see.
The filter works for one person but not another
Check whether the query uses currentUser(). That function returns issues assigned to the person viewing the board, so different teammates should expect different results.
Permissions can also affect visibility. A quick filter cannot display an issue to someone who is not allowed to view it.
The quick filter is missing from the board
Make sure you are viewing the board where the quick filter was created. Board settings are separate, so adding a filter to a team board does not add it to a project board automatically.
If it is still missing, refresh the board and ask a board administrator to confirm the change was saved. Also check whether the board’s layout or current Jira interface places the filter controls in a different area.
Two active filters hide too much work
Switch off one filter at a time to see which condition removes the issues. Filters that seem compatible by name may overlap in a way that leaves no matching tickets.
For example, Assigned to Me and Unassigned Bugs cannot return the same issue set. Use each on its own, or create a combined query that expresses a different goal.
ONES.com Solution for Project and Knowledge Management
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project is the project management product and a Jira alternative; ONES Wiki is the knowledge base product and a Confluence alternative. They are sold separately.

For teams reviewing their project workflow, ONES Project offers Jira-compatible workflows, sprint management, custom workflows and fields, automation, and built-in reporting. The aim is to help teams organize work with less reliance on extra plugins, while keeping deployment choices open.
Core capabilities
- Pain: Teams want to keep familiar Jira-style workflows. ONES capability: ONES Project supports Jira-compatible workflows. Result: Teams can preserve recognizable work patterns while evaluating a Jira alternative.
- Pain: Plugin dependencies can add complexity to project administration. ONES capability: Built-in reporting and automation cover common project needs. Result: Teams can reduce plugin reliance for supported workflows.
- Pain: Standard fields may not match a team’s intake process. ONES capability: Custom fields let teams capture project-specific details. Result: Work can be categorized around the team’s actual process.
- Pain: A generic workflow may not reflect approval or delivery stages. ONES capability: Custom workflows support tailored status paths. Result: Teams can model work in a way that fits their operating needs.
- Pain: Agile teams need a clear view of sprint work. ONES capability: Sprint management supports planning and delivery workflows. Result: Teams can coordinate sprint activities within the project management product.
- Pain: Different organizations have distinct hosting requirements. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can select an environment that meets their operational constraints.
- Pain: A team may need to move between hosted and self-hosted deployment models. ONES capability: The cloud and self-hosted versions have full feature parity. Result: Deployment choice does not mean accepting a reduced feature set.
- Pain: Teams want to evaluate a platform before committing broadly. ONES capability: The free plan supports up to 30 seats. Result: A team can try the project workflow with a limited group.
Application scenarios
Growing software team: A team managing sprints and release work can use ONES Project’s workflows, custom fields, reporting, and automation to organize delivery. It can assess whether the available capabilities fit its needs before changing established practices.
Organization with deployment constraints: A team that cannot use a standard cloud environment can consider On-Premise, Private Cloud, or Air-gapped deployment. Full feature parity across cloud and self-hosted versions helps keep capability needs in the conversation alongside hosting requirements.
Project and knowledge workflows: A company that wants project management and knowledge management under the ONES.com umbrella can consider ONES Project and ONES Wiki. Because they are sold separately, it can assess each product for the work it needs to support.
Frequently Asked Questions
Who can create Jira quick filters?
In most cases, you need permission to administer or configure the board. If the board settings do not show an option to manage quick filters, contact the board owner or a Jira administrator. They can check your access or add the query for you. You can still select and use available quick filters if you have permission to view the board.
Can I use several quick filters at once?
Yes, many Jira boards let you turn on multiple quick filters. The selected conditions narrow the displayed issues together, so an issue generally needs to satisfy the active filters. If the board becomes empty, switch filters off one at a time. This reveals whether the combination is too restrictive or whether one query needs correction.
Do Jira quick filters change the board’s main filter?
No. A quick filter temporarily narrows what you see on the board; it does not change the board’s main filter. The main filter sets the issue scope available to that board. If an issue is outside that scope, selecting a quick filter cannot make it appear. Check the main filter when expected issues remain missing with all quick filters turned off.
Why does a quick filter show different issues for different people?
A query using currentUser() depends on who is viewing the board, so different people will see issues assigned to themselves. Jira permissions can also affect which issues each person can view. To diagnose the difference, compare the JQL, the issue assignees, and each person’s access. A different result does not necessarily mean the filter is misconfigured.
Conclusion
Jira quick filters give you a practical way to focus a shared board without changing its main issue scope. Start with a real team question, write a clear JQL condition, and test the result before inviting everyone to use it.
Keep the filter list purposeful, check combinations, and revisit queries as your project changes. That turns a crowded board into a more useful view of the work that needs attention—without making every question a separate board configuration.