How to Create a Filter in Jira: A Step-by-Step Guide (2026)
Need to know how to create a filter in Jira? Follow this step-by-step 2026 guide to save searches, reduce clutter, and track issues faster. Read now!
Jira can help you answer almost any project question, but finding the right issues often becomes the hardest part. You may need to locate overdue bugs, review one team’s sprint work, or track tickets assigned to you. Without a saved filter, you repeat the same searches and risk missing important updates.
That repetition creates clutter quickly. Teams may build slightly different searches, share unclear links, or rely on dashboards that show too much. A small mistake in a query can hide high-priority work.
But here's the truth: creating a Jira filter only takes a few minutes once you understand JQL and the saving options. This guide shows you how to build a filter, save it, share it, edit it, and use it in dashboards during 2026.
How to Create a Filter in Jira
To create a filter in Jira, open Issues or Search for issues, define your criteria with the basic search or JQL, run the search, and select Save as. Give the filter a clear name, then choose who can view or edit it.
For example, you could create a filter that shows unresolved bugs assigned to you:
project = PAY AND issuetype = Bug AND assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC
The exact menu label can vary between Jira Cloud and self-managed Jira. The general process remains the same.
Step 1: Open Jira Issue Search
- Sign in to Jira.
- Open the Issues menu.
- Select Search for issues, View all issues, or the equivalent search option.
You should arrive at a page showing an issue search panel. This is where you create, test, save, and manage filters.
If you already have an existing filter open, select the option to switch to advanced search or start a new search. Starting clean helps prevent old conditions from affecting your results.
Step 2: Choose Basic or Advanced Search
Jira usually offers two ways to build a search:
- Basic search: Choose fields and values through menus.
- Advanced search: Write a JQL query directly.
Basic search works well when you need a quick query, such as all open tasks in a project. Advanced search gives you more control over dates, functions, ordering, and combined conditions.
You can begin with basic search and switch to advanced search when the query becomes more specific. Jira may generate JQL automatically after you choose several criteria.
Step 3: Add the Main Criteria
Start with the condition that narrows the search most effectively. Common fields include project, issue type, status, assignee, priority, sprint, labels, and due date.
For example, a product manager may want all unresolved stories in the current sprint:
project = APP AND issuetype = Story AND sprint in openSprints() AND resolution = Unresolved
A support lead may need urgent incidents that remain open:
project = HELP AND issuetype = Incident AND priority in (Highest, High) AND statusCategory != Done
Begin with two or three conditions. You can add more after checking whether the results are useful.
Step 4: Refine the Query with JQL
JQL, or Jira Query Language, lets you describe exactly which issues should appear. A basic query follows this pattern:
field operator value
Here are common examples:
| Purpose |
Example JQL |
| Issues assigned to you |
assignee = currentUser() |
| Unresolved work |
resolution = Unresolved |
| Recently updated issues |
updated >= -7d |
| High-priority bugs |
issuetype = Bug AND priority in (Highest, High) |
| Issues in several projects |
project in (APP, PAY, HELP) |
| Items due soon |
duedate <= 7d AND statusCategory != Done |
Use AND when every condition must be true. Use OR when any condition can be true. Parentheses make complex logic easier to read:
project = APP AND (priority = Highest OR labels = customer-impact) AND statusCategory != Done
Let me explain: a filter becomes valuable when its conditions match a real decision. If a team reviews customer-impacting work every morning, the query should reveal precisely that work.
Step 5: Run and Check the Results
Select Search or Run to display matching issues. Review the results before saving the filter.
Check three things:
- Are important issues missing?
- Are unrelated issues appearing?
- Will the results remain useful tomorrow?
For example, a query using a fixed sprint name may stop working after the sprint ends. A query using openSprints() may remain useful for recurring sprint reviews.
Also inspect the columns shown in the results. Add fields such as priority, assignee, status, sprint, story points, or due date when they support the decision you need to make.
Step 6: Save the Filter
When the results look correct, select Save as. Enter a descriptive name that tells people what the filter shows and who should use it.
Good names include:
- My unresolved high-priority bugs
- Current sprint stories for the mobile team
- Customer-impacting issues awaiting review
- Open incidents due this week
Avoid names such as “My filter,” “Test search,” or “New query.” Those names become difficult to recognize when a team owns dozens of saved searches.
Step 7: Set Access Permissions
After saving, open the filter’s details or manage-filters area. Choose whether the filter is private or shared with specific people, groups, teams, or projects.
Keep personal work private when it contains temporary planning criteria. Share operational filters when other people depend on the same view.
You may need Jira administrator permissions to share a filter broadly. If a sharing option is unavailable, ask an administrator to check the relevant permission settings.
Step 8: Confirm the Filter Works for Other People
Sharing a filter does not always guarantee that everyone sees identical results. People may lack project permissions, issue security access, or access to a custom field.
Ask a teammate to open the filter and verify the results. This simple check can reveal permission problems before a meeting or reporting cycle.
JQL Building Blocks That Make Filters More Useful
JQL becomes easier when you treat each condition as a question. “Which project?” uses project. “Who owns it?” uses assignee. “When did it change?” uses updated.
Use Current-Time Functions for Recurring Views
Relative functions prevent you from updating a filter every week. For example:
updated >= -14d
This query shows issues updated during the last 14 days. A fixed date would continue showing the same period, while the relative condition moves forward automatically.
Other useful functions include startOfDay(), endOfDay(), startOfWeek(), and openSprints(). Availability can vary by Jira version and configuration.
Use Ordering to Put Attention First
A search can return the right issues while presenting them in an unhelpful order. Add an ORDER BY clause to improve review speed.
project = APP AND statusCategory != Done ORDER BY priority DESC, updated DESC
This places higher-priority work first, then shows the most recently updated issues within the same priority level.
Use Labels Carefully
Labels are flexible, but spelling differences can split related work. For example, customer-impact, customer_impact, and customerimpact may represent three separate label values.
Agree on a naming convention before creating many filters around labels. A short team rule can prevent hours of cleanup later.
Use Functions Instead of Hard-Coded Names
assignee = currentUser() is more reusable than naming one person. Each viewer sees their own assigned issues, which makes the filter suitable for a team dashboard.
Similarly, project in projectsLeadByUser() may help project leads review projects they manage, depending on the Jira functions enabled in your environment.
How to Edit, Copy, and Organize Saved Filters
You can change a saved filter whenever the team’s workflow changes. Open the saved filter, adjust the query, run it, and select the save option again.
Be careful when editing a shared filter. A small change can alter a dashboard gadget, board, or recurring review used by several people.
Copy a Filter Before Making Major Changes
Copying a filter creates a safer working version. This is useful when you want to test a new condition without changing a team-wide view.
For example, copy “Open incidents due this week” before adding a condition for a new support region. Compare both results, then replace the old version only after the team agrees.
Use Favorites for Frequent Searches
Favorite filters are easier to reach from Jira navigation. Keep this list focused on searches you open regularly.
A practical set might include:
- Your current sprint work
- Unassigned high-priority issues
- Recently reported bugs
- Blocked work awaiting action
Remove old favorites periodically. A short list reduces the time you spend searching for the right search.
Review Ownership and Usage
Shared filters can outlive the people who created them. Review ownership when team members change roles or leave a project.
Jira administrators may have tools for finding unused or privately owned filters. A quarterly review can reduce clutter and prevent broken dashboards.
Common Filter Examples for Jira Teams
The best filter depends on the decision you want to support. Here are practical examples for common roles.
For Individual Contributors
To see your unfinished work across one project:
project = APP AND assignee = currentUser() AND statusCategory != Done ORDER BY priority DESC
To find work that has not changed recently:
assignee = currentUser() AND statusCategory != Done AND updated < -14d
The second view can help you spot stalled work before it becomes a delivery risk.
For Scrum Masters
To review unresolved work in active sprints:
project = APP AND sprint in openSprints() AND statusCategory != Done ORDER BY status ASC, priority DESC
To identify issues without an owner:
project = APP AND assignee is EMPTY AND statusCategory != Done
An unassigned-work filter is useful during sprint planning because it exposes tasks that may otherwise remain overlooked.
For Engineering Managers
To track recently created bugs:
project = APP AND issuetype = Bug AND created >= -30d ORDER BY created DESC
To examine overdue work:
project = APP AND duedate < now() AND statusCategory != Done ORDER BY duedate ASC
Use date conditions carefully. A due-date filter may miss issues that do not have a due date assigned.
For Product Managers
To review customer-impacting work that is still open:
project = APP AND labels in (customer-impact, escalation) AND statusCategory != Done
To see unresolved stories planned for the next release:
project = APP AND issuetype = Story AND fixVersion = "2026.1" AND resolution = Unresolved
Replace the release name with your team’s actual version value. Naming conventions matter when filters depend on releases.
How Filters Work with Boards, Dashboards, and Reports
A saved filter can become the foundation for several Jira views. Boards can use filters to determine which issues appear. Dashboards can use them for gadgets such as assigned work, pie charts, and two-dimensional summaries.
For example, one filter may show all open defects in a product project. A dashboard gadget can group those defects by priority, while another groups them by assignee.
Here's why filter design matters: every connected view inherits the filter’s logic. If the query excludes subtasks, a dashboard built on that query may also exclude them.
Choose Filters for a Specific Purpose
A filter for daily work should stay focused. A filter for leadership reporting may need broader conditions and stable categories.
Trying to serve both purposes with one query often creates confusion. A developer needs actionable issues, while an executive may need trends by project, priority, or status.
Test Dashboard Results Independently
Open the saved filter directly before trusting a dashboard gadget. Confirm that the gadget uses the intended filter and that its date range matches your reporting period.
For example, a dashboard may display 42 open bugs while the direct search displays 39. The difference could come from gadget caching, additional gadget settings, or different permissions.
Jira Filter Solution: ONES.com
ONES.com brings project management and knowledge management into one platform, with ONES Project providing Jira-compatible project workflows. It can help teams organize work, create structured views, and reduce the need to connect several separate plugins.
ONES Project is sold separately from ONES Wiki. The platform supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions. A free plan supports up to 30 seats.
Core Capabilities
- Scattered issue tracking → Jira-compatible workflows → Teams can use familiar project patterns for planning, assigning, and tracking work without redesigning every process.
- Repeated manual searches → Custom workflows and fields → Teams can structure issue information around their own review stages and operational requirements.
- Limited visibility into sprint work → Sprint management → Teams can plan active iterations and review progress through views aligned with sprint activity.
- Too many disconnected reporting steps → Built-in reporting → Managers can inspect project progress through native reporting capabilities instead of assembling every view separately.
- Plugin-heavy customization → Native project capabilities → Teams can reduce dependence on extra extensions for common workflows, fields, automation, and reporting needs.
- Manual status updates → Automation → Repetitive actions can follow defined conditions, helping teams reduce routine coordination work.
- Deployment restrictions → Multiple deployment choices → Organizations can select Cloud, On-Premise, Private Cloud, or Air-gapped deployment according to their environment.
- Separate work and knowledge spaces → ONES Project plus ONES Wiki → Teams can connect project activity with team knowledge while keeping the products separately available.
Application Scenarios
Software development team: A development group can use custom workflows for discovery, implementation, review, testing, and release. Built-in reporting can then support sprint reviews without requiring several add-ons.
Restricted-network organization: A team operating in an air-gapped environment can select a self-hosted deployment while retaining the same general feature coverage as the cloud version.
Growing product organization: A product team can standardize fields for customer impact, release planning, and priority. Project views can then help product, engineering, and support teams discuss the same work.
Common Challenges When Creating Jira Filters
Challenge: The Query Returns Too Many Issues
Cause: The filter uses broad conditions such as a project alone or an open status category.
Solution: Add a second narrowing condition, such as issue type, assignee, sprint, label, priority, or update period. Test each addition so you understand which condition changes the result.
Challenge: The Filter Shows No Results
Cause: One field value may be incorrect, a project key may be misspelled, or several conditions may conflict.
Solution: Run each condition separately, then combine them gradually. Check exact status names, issue type names, field permissions, and project access.
Challenge: Teammates Cannot Open the Filter
Cause: The filter remains private or the viewer lacks the required project permission.
Solution: Review the filter’s sharing settings and confirm that the intended group or project has access. An administrator may need to adjust permissions.
Challenge: A Recurring Filter Stops Being Useful
Cause: The query uses fixed sprint names, dates, or release values.
Solution: Replace fixed criteria with relative dates or Jira functions where appropriate. For example, use updated >= -7d for a rolling weekly review.
Challenge: A Shared Filter Changes Unexpectedly
Cause: Multiple people edit the same saved filter, or the owner changes its logic without notifying the team.
Solution: Assign an owner, document the filter’s purpose in its description, and copy the filter before testing major changes.
FAQs
Can I create a Jira filter without knowing JQL?
Yes. Jira’s basic search lets you choose fields and values through menus. After the search runs, you can switch to advanced mode to inspect the generated JQL. Learning a few operators later gives you more control over dates, functions, ordering, and combined conditions.
How do I share a saved Jira filter?
Open the filter’s details or manage-filters area, then change its permissions from private to a permitted group, project, or other sharing option. You may need administrator support for broad sharing. Each viewer still needs permission to see the matching issues.
What is the difference between a Jira filter and a dashboard?
A filter defines which issues match a search. A dashboard presents information through gadgets, charts, and lists. A dashboard can use one or more saved filters, so the filter controls the underlying issue set while the dashboard controls presentation.
Why does my Jira filter return different results for different people?
Jira permissions can affect which issues each person can see. Issue security, project access, and custom-field permissions may also change results. Functions such as currentUser() intentionally return different results for different viewers.
Can I use a filter for an active sprint?
Yes. A query such as sprint in openSprints() can show issues in active sprints, subject to your Jira version and configuration. Add project, issue type, or status conditions to make the view more useful for sprint planning or review.
Conclusion
Creating a Jira filter is a simple process: open issue search, define criteria, run the query, save it, and configure access. The strongest filters answer a specific project question and remain useful as work changes.
Start with a practical view, such as your unresolved work or the current sprint’s blocked issues. Then refine the JQL, add helpful columns, test permissions, and connect the filter to dashboards when necessary.
But here's the truth: a filter only helps when people trust its results. Clear naming, focused criteria, relative dates, and regular ownership reviews keep that trust intact. If your team needs broader project workflows, reporting, automation, and flexible deployment options, ONES.com offers an alternative path through ONES Project.