How to Create a Jira Filter: Steps, JQL, and Sharing Guide
Tired of repeating Jira searches? Learn how to create a jira filter with JQL, save it, and share it—click to make team updates easier.
A Jira filter saves a search so you can find the issues you need without rebuilding the same query each time. Create one by searching with basic filters or JQL, selecting Save as, and choosing who can view it.
But here's the truth: a search that works for you may be useless to your team if it is too broad, poorly named, or private. A small JQL mistake can also hide important work or fill your results with unrelated issues.
That can turn simple tasks—like checking your open sprint work or finding overdue bugs—into repeated searching and missed updates. Sharing the wrong filter can create confusion about which results teammates should trust.
Here's why a clear filter matters: it gives you a reusable view of relevant issues, with access settings that match your team. Follow these steps to build, save, refine, and share one confidently.
How to Create and Share a Jira Filter
Start with the issue search, confirm the results, and save the query as a filter. Then review its permissions before sharing it.

1. Open Jira issue search
Sign in to Jira and open Filters or Issues, depending on your Jira version.
Choose Search for issues or the equivalent issue-search option. You may see a basic search view with fields such as project, status, and assignee.
2. Build your search
Use basic search when you need a quick query, such as issues assigned to you in one project. Choose JQL when you need more control over conditions, dates, sorting, or multiple projects.
For example, to find unfinished issues in a project and sort by recent updates, enter:
project = ABC AND statusCategory != Done ORDER BY updated DESC
Replace ABC with your project key. Select Search or Run, then check whether the results match your intent.
3. Save the search as a filter
Select Save as near the search controls. Jira may ask you to save the current search first if you have made changes.
Give the filter a clear name, such as ABC: Open issues by latest update. Add a description if teammates may need context.
Save the filter, then use Details or the filter settings to review its owner and access permissions.
4. Set permissions and share
Open the filter’s details or manage-permissions screen. Choose the audience your Jira setup allows, such as a group, project, or project role. Options vary by Jira version and administrator settings.
Give view access when teammates only need to see results. Grant edit access only when they should be able to change the saved filter. People still need permission to view the underlying projects and issues.
5. Make it easy to find and maintain
Add the filter to your favorites so it appears in your filter menu. If you use a Jira dashboard, add an appropriate filter gadget and select your saved filter.
Revisit the query when project keys, workflows, or team responsibilities change. If you edit the search later, save those changes to update the filter rather than assuming every search change is saved automatically.
JQL Basics for Useful Jira Filters
JQL is Jira’s query language for finding issues through conditions and operators. A query commonly combines a field, an operator, and a value, then adds further conditions with AND or OR.
For example, assignee = currentUser() finds issues assigned to the person running the query. Add AND statusCategory != Done to narrow the results to unfinished work.
Start with fields, operators, and values
Fields describe issue details, including project, status, assignee, priority, and updated. Operators such as =, !=, IN, and IS EMPTY help you compare or check those fields.
Try this query to find unresolved high-priority bugs in a project:
project = ABC AND issuetype = Bug AND priority = High AND resolution IS EMPTY
Check your Jira field names and project values if the search returns an error or unexpected results. Teams can customize fields, and some fields may have different names in different Jira environments.
Use parentheses to control logic
JQL evaluates conditions in a particular order, so parentheses make mixed AND and OR logic easier to read. For example:
project = ABC AND (priority = High OR labels = customer-impact)
This query finds high-priority issues or issues marked with the specified label, within project ABC. Without parentheses, the results may not reflect the grouping you intended.
Sort results for the job at hand
Add ORDER BY to put the most useful issues first. A support lead might sort by priority, while a project manager may want recently updated issues at the top.
For example, project = ABC AND statusCategory != Done ORDER BY priority DESC, updated DESC sorts unfinished issues by priority and then by update time. Confirm that the sort order supports the task rather than simply looking tidy.
Jira Filter Examples You Can Adapt
These queries are starting points, not universal templates. Replace project keys, labels, and field values with the ones your Jira project uses.
See your unfinished work
assignee = currentUser() AND statusCategory != Done ORDER BY duedate ASC
This can help you review your open work by due date. If your team does not use due dates consistently, sort by updated DESC instead.
Find recently updated issues in a project
project = ABC AND updated >= -7d ORDER BY updated DESC
This query finds issues updated within the past seven days. It can help you prepare for a weekly review, although it does not identify who made each update.
Review overdue, unfinished issues
project = ABC AND duedate < now() AND statusCategory != Done ORDER BY duedate ASC
Use this view to spot issues that have passed their due dates and remain unfinished. Check whether your team treats missing due dates differently, since those issues will not appear in this result.
Check work in a sprint
project = ABC AND sprint in openSprints() AND statusCategory != Done
This can give you a quick view of unfinished work in active sprints. Sprint functions and the fields available to you can depend on your Jira configuration.
How to Share Filters Without Creating Confusion
A saved filter can be private, shared with a group, or made available through project-related permissions, depending on your setup. Choose the narrowest audience that can still do the work.
For example, a team lead might share a sprint review filter with the project’s delivery group. A personal list of assigned issues usually does not need broad access.
Check both filter access and issue access
Sharing a filter does not automatically grant people access to every issue it returns. A teammate may be able to open the filter but see fewer results because their project permissions differ from yours.
Test the filter with a teammate or an appropriate account when possible. This can reveal access gaps before a review meeting or handoff.
Use clear names and descriptions
A name like Open issues may be unclear if your team has several projects. A more useful name could be ABC: Open bugs for triage, with a description explaining the intended audience or review routine.
Good naming also helps when a dashboard contains several saved searches. Teammates can identify the right filter without opening each one.
Consider subscriptions and dashboards
If your Jira setup allows filter subscriptions, you may be able to receive scheduled updates by email. Review the recipients and schedule so the messages remain useful rather than noisy.
A dashboard gadget can display saved-filter results in a shared view. Check gadget access as well as filter permissions, since dashboard visibility and issue visibility may involve separate settings.
Value proposition: If your team is reviewing how it manages work beyond saved searches, ONES.com brings project management and knowledge management together. ONES Project is a Jira alternative, while ONES Wiki is a Confluence alternative; the products are sold separately.

Creating a Jira filter is a focused way to organize issue searches. Teams may also need workflows, sprint planning, reporting, and internal knowledge in the same operating environment. ONES.com offers a broader option for teams assessing those needs, including teams that require self-hosting.
Core capabilities: team needs and practical outcomes
Need: Keep project work and team knowledge connected. Capability: ONES.com combines project management and knowledge management, powered by ONES Assistant. Result: Teams can plan work and manage knowledge within one platform; ONES Project and ONES Wiki remain separate products.
Need: Move from Jira without discarding familiar workflow patterns. Capability: ONES Project supports Jira-compatible workflows. Result: Teams can work with familiar process structures while evaluating a Jira alternative.
Need: Reduce reliance on add-ons for common project routines. Capability: ONES Project includes built-in reporting, automation, sprint management, custom workflows, and custom fields. Result: Teams can handle these needs with native capabilities and potentially fewer plugins.
Need: Choose where project management is hosted. Capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Organizations can select a deployment model that fits operational and security requirements.
Need: Keep features consistent across hosting choices. Capability: ONES.com provides full feature parity between cloud and self-hosted versions. Result: Teams can assess deployment options without planning around a reduced feature set for self-hosting.
Need: Explore the platform before a broader rollout. Capability: The free plan supports up to 30 seats. Result: A small team can evaluate its fit before planning wider adoption.
Need: Manage recurring project work with less manual coordination. Capability: ONES Project supports sprint management and automation. Result: Teams can organize sprint work and automate suitable routine steps.
Need: Adapt project tracking to a team’s process. Capability: ONES Project supports custom workflows and fields. Result: Teams can represent their work without relying only on default process structures.
Application scenarios
A product team assessing a Jira alternative: The team can compare its existing workflow, sprint routines, custom fields, and reporting needs with ONES Project’s capabilities. This creates a practical evaluation around how the team works, rather than around a feature checklist alone.
An organization with deployment requirements: A team that needs cloud, private cloud, on-premise, or air-gapped deployment can examine the available ONES.com options. Feature parity across cloud and self-hosted versions helps keep that evaluation focused on deployment fit.
A team organizing project work and knowledge: An organization can consider ONES Project for project management and ONES Wiki for knowledge management. Because they are sold separately, the team can assess each product against its own requirements.
Common Jira Filter Challenges
Problem: The query returns too many issues. Add a project, status, assignee, or date condition. For instance, add project = ABC to a broad unfinished-work query when you only need one project.
Problem: The query returns no results. Check the project key, field value, spelling, and access permissions. Try removing one condition at a time to find which part excludes the issues you expect.
Problem: Teammates cannot see the same results. Review filter-sharing permissions and confirm that teammates have access to the relevant projects and issues. A shared filter cannot override Jira’s project permissions.
Problem: A saved filter seems out of date. Confirm that you saved recent query edits. Also review whether the filter’s criteria still match current project fields, statuses, and team practices.
Problem: The team cannot find the right filter. Use a consistent naming pattern that includes the project or purpose. Add a short description and mark frequently used filters as favorites where available.
Frequently Asked Questions
Can I create a Jira filter without using JQL?
Yes. Basic search lets you select common criteria, such as project, status, or assignee, without writing a query. When the results look right, save the search as a filter. JQL is helpful when you need more control, such as combining several conditions or sorting results in a specific order.
How do I share a Jira filter with my team?
Open the saved filter’s details or permissions settings and choose an audience your Jira configuration supports. You may be able to share it with a group, project, or project role. Give people view access if they only need the results. They also need permission to view the issues themselves.
Why can a teammate see fewer results than I can?
Jira applies issue and project permissions to each person viewing a filter. Sharing the saved search does not grant access to its issues. Ask an administrator to review the teammate’s project permissions, and check whether the query relies on fields or project values available to that person.
What is the difference between a Jira search and a filter?
A search is the query you run to find issues. A filter is the saved version of that search, which you can reopen, share, favorite, or use in supported dashboard gadgets and subscriptions. Saving a search makes it reusable, while the JQL or basic criteria define which issues appear.
Conclusion
To create a Jira filter, build a basic search or JQL query, check the results, save the search, and set appropriate permissions. A clear name and a quick access check make the filter easier to use across your team.
When a query feels unreliable, test its conditions one by one and confirm that teammates can access the underlying issues. If your needs extend beyond saved searches into project workflows, sprint management, reporting, or deployment choices, ONES.com may be worth evaluating as a broader Jira alternative.