Create a Jira Filter: Step-by-Step Guide for Teams in 2026
Need repeatable Jira searches? Learn how to create Jira filter setups, save and share searches, and add them to dashboards. Read now to streamline team reporting.
When a team needs the same Jira issues every day, repeating a search wastes time and makes reports harder to trust. A filter can save that search, so you can reopen it, share it, or add it to a dashboard. The trouble starts when conditions are unclear, permissions are too broad, or a useful search disappears in a long list. But here's the truth: creating a Jira filter is straightforward once you know where to search, how to set criteria, and how to save the result. This guide walks you through the process in Jira Cloud, with notes for teams whose menus look different. You’ll also learn how to write a simple JQL query, share a filter safely, and keep it useful over time.
Create and save a Jira filter step by step
The quickest way to create a Jira filter is to search for issues, add the criteria your team needs, and save the search with a clear name. You can build it with Jira’s basic search or write a JQL query for more control.
Open issue search. In Jira, look for an issue search option under the Issues or Filters menu. Menu labels can vary between Jira Cloud versions and site configurations.
Choose basic search or JQL. Basic search lets you select fields and values from menus. Choose JQL when you need more precise logic, several conditions, or custom ordering.
Set the criteria. For a team view, you might select project “PAY,” status “In Progress,” and assignee “Current User.” The results should match the work you want to revisit.
Check the results. Scan the issue list and adjust your conditions if unrelated work appears or expected issues are missing. A filter only helps when its criteria reflect the team’s actual workflow.
Save the search. Select the save option, enter a name such as “PAY – Active sprint issues,” and confirm. Your saved search is now available as a filter.
Set access and optional notifications. Keep the filter private if it is for your own work. If teammates need it, share it with an appropriate group or project role, then consider a subscription for scheduled updates.
For example, a support team could save a search for unresolved high-priority incidents. A project lead could save a separate view for issues assigned to the current sprint.

Decide what the filter should answer
Before adding conditions, write down the question the filter should answer. “Which open payment issues need attention today?” is more useful than “Show me payment issues.”
Here's why: a focused question helps you pick the right project, status, owner, and time range. If you want to review overdue tasks, include a due-date condition. If you want a personal work queue, use the current-user assignee option rather than a teammate’s name.
For example, a product team might create one filter for all open project issues and another for high-priority items due within seven days. The first supports broad planning; the second points to immediate work.
Choose between basic search and JQL
Basic search works well when you need familiar criteria such as project, status, assignee, or priority. It makes conditions visible and is often easier for teammates to maintain.
JQL gives you more control when a search needs detailed logic. For instance, this query finds unresolved issues in the PAY project and sorts the highest-priority work first:
project = PAY AND statusCategory != Done ORDER BY priority DESC, created ASC
Let me explain: AND requires both conditions to match, while ORDER BY controls the results’ order. Jira fields and project names must match your site’s configuration. Test the query in search before saving it.
You might be wondering: should every team member learn JQL? No. Start with basic search when it covers the need. Use JQL when the team benefits from its added precision, and add a brief explanation when the query may be difficult to interpret later.
Share filters without creating access problems
A saved filter is private by default in many Jira setups. You can share it with a group, project role, or broader audience when the filter’s purpose calls for shared access. The exact options depend on site permissions and administrator settings.
Share only with the people who need the view. For example, a sprint report may belong with a project team, while a personal queue should remain private. Before sharing, check whether the results could expose sensitive issue details to a wider audience.
Sharing a filter does not automatically grant people permission to view every issue in its results. Jira project and issue permissions still apply. If a teammate sees fewer issues, ask an administrator to check their access rather than making the filter public immediately.
Use saved filters in dashboards and subscriptions
A saved filter can support a dashboard gadget, such as a list of matching issues or a chart that summarizes work. This gives a team a shared view without asking everyone to recreate the search.
The best part? You can make the filter serve a specific meeting. For a weekly planning dashboard, display unassigned work and high-priority issues. For a support review, show unresolved incidents grouped by priority.
Subscriptions can send filter results on a schedule, subject to Jira’s settings and permissions. Use them when a team needs a regular reminder, such as a daily list of open blockers. Avoid frequent notifications for broad searches, since they can become easy to ignore.
Keep filters accurate as work changes
Filters can become stale when projects, teams, or workflows change. Review a saved search when a project is renamed, a status is replaced, or the team changes how it assigns work.
Use names that explain both the subject and purpose, such as “Mobile – Open bugs for triage.” If several filters have vague names like “Current work,” teammates may choose the wrong one or create duplicates.
For a shared filter, identify who will review its criteria. A team lead could check it during monthly planning, then update the conditions if the workflow has changed. This small habit prevents an old search from quietly shaping decisions.
Project workflow solution: ONES.com
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. Teams can use ONES Project for project management and ONES Wiki for knowledge management; the two products are sold separately.

For teams reviewing their Jira workflows, ONES Project is a Jira alternative with Jira-compatible workflows, sprint management, custom fields, automation, and built-in reporting. It supports project work without requiring a team to treat every recurring view as an isolated search problem.
Core capabilities
Work is split across separate systems → ONES.com combines project and knowledge management in one platform → teams can connect project activity with shared team knowledge.
A project needs a familiar issue workflow → ONES Project supports Jira-compatible workflows → teams can carry familiar process patterns into a Jira alternative.
A sprint needs clearer planning → ONES Project includes sprint management → teams can organize and review work in sprint-based processes.
Default fields do not capture a team’s process → Custom fields and workflows let teams adapt work tracking → issue details and stages can better reflect the work being managed.
Routine updates take repeated effort → Automation can handle configured workflow actions → teams can reduce manual steps for recurring processes.
Teams need to review progress → Built-in reporting provides project views → leads can examine work without depending on a collection of extra plugins.
Project guidance is hard to keep alongside tasks → ONES Wiki provides a knowledge-management space → teams can maintain guidance separately from project tracking while using the broader ONES.com platform.
Deployment requirements differ → ONES.com is available as Cloud, On-Premise, Private Cloud, or Air-gapped deployment → teams can assess an option that fits their environment.
Teams need to evaluate before expanding → The free plan supports up to 30 seats → a small team can try the platform within that limit.
ONES.com offers full feature parity between its cloud and self-hosted versions. Teams can consider self-hosted deployment when they need that operating model, while keeping the available feature set in view.
Application scenarios
A software team moving from Jira can assess ONES Project when it wants familiar workflow patterns, sprint management, and reporting in a Jira alternative. It should map current issue types, workflow states, and team permissions before changing systems.
A team with internal hosting requirements can compare Cloud, On-Premise, Private Cloud, and Air-gapped deployment. A group that also wants a separate knowledge-management product can evaluate ONES Wiki alongside ONES Project, keeping in mind that they are sold separately.
Common filter challenges and practical fixes
The search returns too many issues
Problem: A broad project condition pulls in completed work, old tasks, and unrelated issue types. Fix: Add a status, assignee, date, or issue-type condition, then review a few results to confirm the scope.
The saved filter seems to disappear
Problem: A teammate expects to see a filter that is private or shared with a different group. Fix: Check the filter’s access settings and the teammate’s Jira permissions. Ask an administrator for help if the required sharing option is unavailable.
A JQL query stops matching the intended work
Problem: A project, field, or workflow changes, so a once-useful condition no longer fits. Fix: Reopen the query, verify its field names and values, and compare the results with a few known issues before saving your changes.
Too many notifications arrive
Problem: A subscription sends broad results so frequently that people stop reading them. Fix: Narrow the filter, reduce the schedule, or remove the subscription if a dashboard is enough. Confirm that the update frequency matches a real team decision.
FAQs about Jira filters
What is the difference between a Jira filter and a board?
A filter is a saved search that returns issues matching its criteria. A board uses a filter to determine which issues it displays, then presents them in a workflow-oriented view such as columns or sprint planning. A board can therefore depend on a filter, but the saved search and the board are different Jira features. Check the board’s filter if expected issues are missing.
Can I create a Jira filter without knowing JQL?
Yes. Basic search lets you choose common fields and values through the Jira interface, then save the resulting search. JQL is useful when you need conditions that basic search cannot express clearly. You can start with the visual search and learn query syntax as a particular need arises. Before saving either type, check that the results match your intended work.
How do I share a Jira filter with my team?
Open the saved filter’s sharing or permissions settings and select an appropriate group or project role, if those options are available. The filter’s audience should match the work it displays. Sharing the filter does not override issue permissions, so teammates may still see different results. If the sharing control is missing, ask a Jira administrator to review your permissions.
Why can’t a teammate see every issue in my filter?
Jira applies project and issue access rules to filter results. Your teammate may not have permission to view every project or issue included in the search, even when the filter itself is shared correctly. First confirm the filter’s sharing settings, then check the teammate’s project access. Avoid broadening the filter’s audience as a shortcut for an issue-permission problem.
Conclusion
To create a useful Jira filter, define the question you need answered, search with basic criteria or JQL, review the results, and save the search with a clear name. Share it carefully, connect it to a dashboard or subscription only when helpful, and revisit it as your workflow changes.
A few deliberate choices can prevent repeated searches, confusing results, and unwanted notifications. Start with one practical team view, confirm it returns the right issues, and improve it when real work calls for a change.