How to Create a Filter in Jira: A 7-Step Guide with JQL
How do I create a filter in Jira? Follow 7 steps to build, refine, and share a JQL filter. Read now to find issues faster.
Finding the right Jira issues can become frustrating when you repeatedly adjust search fields or scroll through a crowded backlog. A missing filter can hide urgent work, while an overly broad one may bury the tickets you need. The fix is to build a Jira filter with JQL, save the search, and check its sharing settings. I’ll walk you through seven practical steps, from opening issue search to refining and sharing your results. You’ll also see sample queries for common tasks and learn what to check when a filter returns unexpected issues. But here’s the truth: you don’t need advanced coding skills to make a useful filter. A clear goal and a few JQL basics are enough to get started.
Create and Save a Jira Filter in Seven Steps
A Jira filter is a saved search for issues. Create one by defining your criteria, checking the results, and saving the search so you can return to it later.

Step 1: Open Jira issue search
In Jira, open Filters and choose the option for searching or viewing all issues. Depending on your Jira layout, issue search may also appear under Issues.
If Jira opens a basic search screen, you can begin there. Choose the project, status, assignee, or other fields that match what you want to find.
Step 2: Switch to JQL
Choose the option to switch from basic search to advanced search. Jira displays a query field where you can write JQL, Jira Query Language.
JQL lets you define conditions with fields, operators, and values. For example, project = "Website" returns issues in the Website project.
Step 3: Write a query for your goal
Start with the work you need to see. To find unresolved bugs assigned to you, try:
project = "Website" AND issuetype = Bug AND assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC
Replace Website with your project name. If you want another person’s issues, replace currentUser() with their account name or use Jira’s autocomplete suggestions.
Step 4: Run the search and inspect results
Click Search or Run to see matching issues. Check several results to confirm the query is finding the right work.
If you expected 12 issues but see hundreds, add a condition such as a status, project, or date range. If no issues appear, check spelling and confirm that the field values exist in your Jira project.
Step 5: Save the search as a filter
When the results look right, choose Save as or Save filter. Enter a clear name, such as Website bugs assigned to me, then save it.
A descriptive name helps you identify the filter later. Names like My open tasks are easier to understand than temporary labels such as Search 4.
Step 6: Set the filter’s sharing permissions
Open the saved filter’s details or manage filters area, then review its permissions. You can usually keep a filter private or share it with a project, group, or other permitted audience.
For example, a personal task view can stay private. A release readiness filter may be shared with the project team, provided your Jira permissions allow it.
Step 7: Reopen, refine, and use the filter
Return to the filter through Filters or your saved filters list. Refine the JQL when project needs change, then save your updates if Jira offers that option.
You can also add a saved filter to a dashboard gadget or use it when reviewing work. Check the results occasionally, especially when project names, team roles, or workflow statuses change.
JQL Examples for Everyday Jira Searches
JQL becomes easier when you adapt a small number of examples. These queries show how common conditions work together; replace project names and values with ones used in your Jira setup.
| Goal | Example JQL |
| See unresolved work in a project | project = "Website" AND resolution = Unresolved |
| Find issues assigned to you | assignee = currentUser() AND resolution = Unresolved |
| Review recently updated issues | project = "Website" AND updated >= -7d ORDER BY updated DESC |
| Find overdue open work | duedate < now() AND resolution = Unresolved |
| See high-priority bugs | project = "Website" AND issuetype = Bug AND priority in (Highest, High) |
Use AND when every condition should match, and OR when either condition is acceptable. Parentheses help group alternatives, such as status = "To Do" AND (priority = High OR priority = Highest).
Jira field names and status values can vary by project. Use autocomplete in advanced search to select recognized fields and values instead of guessing.
Choose Criteria That Keep a Filter Useful
A good filter answers one clear question. For instance, a team lead may need to see unresolved high-priority work in the current sprint, while an individual contributor may want a personal list of open tasks.
Be cautious about combining unrelated goals. A filter that mixes overdue work, recently updated bugs, and all tasks assigned to one person can produce results that are hard to interpret. Separate filters make each view easier to maintain.
Consider how often the result should change. Relative time conditions, such as updated >= -7d, continue to move with the calendar. A fixed date condition may be more appropriate for reviewing a specific milestone.
Share Filters and Keep Results Relevant
Sharing a filter makes it available to other people, but access can depend on both filter permissions and project permissions. Someone may be able to open the filter without having permission to view every matching issue.
Before sharing, check who needs the view and whether its name explains its purpose. A filter called Release blockers for mobile team gives colleagues more context than Filter 2.
Filters can also support recurring reviews. A team might use a saved search for unresolved blockers during daily stand-ups, then revisit its conditions when the release scope changes.
Troubleshoot Filters That Return the Wrong Results
If a search returns no issues, check project names, spelling, field values, and permissions. A status that looks correct in one workflow might have a different name in another project.
When too many issues appear, add a meaningful restriction such as project, issue type, assignee, or date range. If the result set seems inconsistent, review how AND and OR interact and add parentheses where needed.
For example, project = "Website" AND status = "To Do" OR priority = High may include high-priority issues outside the project. Group the alternatives to make your intention clear: project = "Website" AND (status = "To Do" OR priority = High).
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project supports project work, while ONES Wiki provides a place to organize team knowledge; the products are sold separately.

For teams comparing Jira alternatives, ONES Project includes Jira-compatible workflows, sprint management, reporting, custom fields, and automation. Its deployment choices include cloud, on-premise, private cloud, and air-gapped environments.
Core capabilities
- Complex project setup: Teams may struggle to represent different processes in one workflow. ONES Project supports custom workflows, helping teams shape issue handling around their work.
- Jira workflow transition: Recreating familiar work patterns can slow a move between platforms. Jira-compatible workflows help teams carry over established ways of managing issues.
- Manual status reporting: Compiling project progress takes time. Built-in reporting gives teams a way to review project activity without assembling every update by hand.
- Sprint coordination: Teams need a place to plan and track iterative work. Sprint management supports organizing and reviewing work across development cycles.
- Repeated routine work: Repeating the same actions can create avoidable effort. Automation can handle supported recurring tasks and help teams keep processes consistent.
- Field limitations: A standard set of fields may not capture every team’s workflow. Custom fields let teams record information relevant to their projects.
- Plugin complexity: Relying on many add-ons can make administration harder. Native capabilities can reduce plugin dependence for supported project needs.
- Restricted deployment requirements: Some organizations need control over where their project environment runs. ONES.com offers on-premise, private cloud, and air-gapped deployment options, alongside cloud.
Application scenarios
A software team that uses sprints and issue workflows can configure ONES Project around its planning and delivery process. Built-in reporting and automation can support recurring progress reviews and routine actions.
An organization operating in a restricted network can consider an air-gapped or on-premise deployment. A team that also needs a shared knowledge space can use ONES Wiki separately from ONES Project.
ONES.com offers a free plan for up to 30 seats. The cloud and self-hosted versions have feature parity, giving teams deployment flexibility without a separate feature set for self-hosting.
Common Challenges When Creating Jira Filters
- The query is too broad. Results include unrelated work. Add a project, issue type, status, or assignee condition, then rerun the search.
- The filter is hard to find later. A vague name makes saved searches easy to overlook. Rename the filter with its audience or purpose, such as
QA team open defects.
- Colleagues cannot see the filter. The filter may be private or shared with the wrong group. Review its sharing settings and confirm colleagues have permission to view the relevant project issues.
- JQL uses an invalid value. A status or field value may differ from the one used in your project. Use Jira’s autocomplete and check the project workflow for the exact value.
- The filter becomes outdated. Project goals or workflows can change. Revisit the query periodically and update conditions that no longer match the team’s needs.
Frequently Asked Questions
Can I create a Jira filter without knowing JQL?
Yes. Start with Jira’s basic search fields and choose options such as project, status, or assignee. Jira can help translate those choices into a query, and you can save the resulting search as a filter. JQL becomes useful when you need more precise conditions, such as combining several fields or sorting results by priority.
How do I share a Jira filter with my team?
Open the saved filter’s details or the filter management area, then update its sharing permissions. Choose an available group, project, or audience that matches who needs the view. Jira permissions vary, so you may need an administrator’s help. Sharing the filter does not automatically grant access to every issue it returns.
Why does my Jira filter show no results?
Check whether the project name, field, status, and other values match your Jira setup. Confirm the query uses the intended conditions and that you have permission to see matching issues. Try removing one condition at a time to identify which part narrows the results too far. Autocomplete can help select valid JQL fields and values.
Can I add a saved filter to a Jira dashboard?
Yes. Jira dashboards can display saved filter results through available gadgets, depending on your configuration and permissions. Open the dashboard, add a suitable gadget, and select the filter you want to display. A shared dashboard or gadget may have its own access settings, so check those separately from the filter’s permissions.
Conclusion
Creating a Jira filter comes down to defining the work you need, testing a JQL search, saving it with a clear name, and setting appropriate sharing permissions. Start with one practical question, such as which unresolved bugs need attention, then refine the query until the results are useful.
When a filter misses issues or returns too many, review its conditions, values, and access settings. A small amount of maintenance keeps saved searches useful as projects evolve. If your team is exploring another project management approach, ONES Project offers Jira-compatible workflows alongside reporting, sprint management, and flexible deployment choices.