How to Create a Filter in Jira: 7 Steps with Real Examples
Wondering how do I create a filter in Jira? Follow 7 clear steps with real JQL examples to track issues without repeating searches. Read now.
To create a filter in Jira, build a search for the issues you need, save it, give it a clear name, and set who can access it. A well-made filter can show overdue work, open bugs, or sprint issues without repeating the same search every day. But a query that looks right can still miss work if it uses the wrong project key, status, or date range. Sharing it incorrectly can leave teammates staring at an empty results list. But here's the truth: you don’t need advanced Jira skills to make a useful filter. I’ll walk you through seven practical steps, with JQL examples you can adapt, plus ways to share, check, and maintain your saved searches.
How to Create a Filter in Jira: 7 Steps
Jira filters are saved searches for issues. You can create one with the visual search builder or write a JQL query, then save and share it for repeat use.
-

Open Jira’s issue search
In Jira Cloud, open Filters or Issues and choose the option to search for issues. The exact label can vary with your Jira version and navigation settings.
Start with the basic search if you’re new to filters. It lets you choose fields such as project, status, assignee, and issue type without writing a query.
-
Choose the fields that define your search
Select the project and criteria that match the work you want to find. For example, choose the project SHOP, status In Progress, and issue type Bug to narrow results to active bugs in that project.
Be specific enough to make the results useful, but don’t add conditions you don’t need. If you choose the wrong project or status, Jira may return no issues even when the work exists.
-
Switch to JQL when you need more control
Choose the advanced search option to see or write the query in Jira Query Language (JQL). JQL is helpful when you need conditions the visual builder doesn’t expose clearly, or when you want a precise date range.
For example, this query finds unresolved bugs in the SHOP project:
project = SHOP AND issuetype = Bug AND resolution is EMPTY ORDER BY priority DESC
JQL field names and available functions can depend on your Jira setup. If a query reports an error, check the field name, project key, and spelling first.
-
Check the results before saving
Review the issues Jira returns. Confirm that they match the purpose of your filter, then adjust conditions that are too broad or restrictive.
For example, if you want work assigned to you, add assignee = currentUser(). If you want open issues updated recently, try statusCategory != Done AND updated >= -7d.
Here's why: checking the results now helps catch mistakes before you share a filter or add it to a dashboard.
-
Save the search as a filter
Choose Save as or Save filter, depending on your Jira version. Enter a name that explains what the search shows, such as SHOP — Unresolved Bugs.
A clear name helps you find the filter later and lets teammates understand its purpose. Avoid names like “My Filter” that don’t describe the results.
-
Set access and sharing permissions
Saved filters are commonly private until you share them. Open the filter’s details or permissions and choose the appropriate people, group, project role, or other sharing option available in your Jira setup.
People also need permission to view the relevant Jira project and issues. If a teammate can open your filter but sees no results, check both the filter’s sharing settings and their project access.
Let me explain: sharing the search makes the filter available, but it does not grant access to issues that a person cannot otherwise view.
-
Use the filter and keep it current
Open the saved filter whenever you want to run the search again. You can also use it in a dashboard gadget, such as Filter Results, if your Jira setup allows it.
Revisit the query when projects, workflows, or team responsibilities change. A filter for the current sprint, for example, may need an updated sprint condition when the team starts a new sprint.
JQL Examples You Can Adapt
The right JQL depends on what you need to see. Start with a small query, check the results, then add conditions one at a time so you can spot which change affects the output.
See your unresolved work
Use assignee = currentUser() AND resolution is EMPTY ORDER BY priority DESC to find unresolved issues assigned to you. This can help you review your queue at the start of the day.
If you want to include issues assigned to your team instead, use a team-specific group or project condition available in your Jira environment. Don’t assume every group name is the same across Jira sites.
Find recently updated open issues
Try project = SHOP AND statusCategory != Done AND updated >= -7d ORDER BY updated DESC to see open SHOP issues updated in the last seven days.
This works well for a weekly review, but it may include tasks that are not important to your meeting. Add a priority or issue-type condition if the results need to be narrower.
Review work in a sprint
Use sprint in openSprints() AND project = SHOP ORDER BY rank ASC to find issues in active sprints for the SHOP project, where the function is supported by your Jira setup.
For a specific sprint, you can use its name or identifier if you know it. Check that the sprint condition returns the expected work before relying on the filter during a planning meeting.
Find overdue issues
Try duedate < now() AND resolution is EMPTY ORDER BY duedate ASC to find unresolved issues with past due dates. If your team doesn’t use due dates consistently, the filter may miss late work.
You might be wondering: why does the same query behave differently across projects? Jira fields, workflows, permissions, and custom configurations can vary. Test a query in the project where you plan to use it.
How to Share a Jira Filter Without Confusion
Choose access based on who needs the filter. A personal task list can stay private, while a team’s triage search may need to be visible to the project team or a named group.
For example, a support lead could share a filter called SUPPORT — Unassigned Critical Bugs with the support project role. The query can help the team find the same work, provided each person has permission to view those issues.
The best part? A useful filter can become part of a dashboard or recurring review. Before doing that, confirm the filter has the right permissions and an owner who can maintain it.
Check access from another account
If possible, ask a teammate with the intended access level to open the filter. Confirm that they can see the saved search and the expected results, rather than relying only on your own administrator view.
When results are missing, check project permissions, issue security settings, and the filter’s sharing rules. Any one of these can affect what another person sees.
Filter Patterns for Everyday Jira Work
Most useful filters answer a recurring question. Decide what you want to know first, then build a query around the project, status, owner, or timeframe that makes the answer actionable.
| Need | Example query | Useful for |
| Unresolved bugs in a project | project = SHOP AND issuetype = Bug AND resolution is EMPTY | Bug triage |
| Issues assigned to you | assignee = currentUser() AND resolution is EMPTY | Daily work review |
| Recently changed open work | statusCategory != Done AND updated >= -7d | Weekly progress checks |
| Issues with past due dates | duedate < now() AND resolution is EMPTY | Deadline follow-up |
Use these as starting points, not fixed recipes. Replace project keys and field values with the ones your Jira team uses, and check the results before saving.
Name filters for quick scanning
A naming pattern can make a busy filter list easier to navigate. For instance, begin with the project key, then describe the issue group: SHOP — Active Sprint Bugs or OPS — Overdue Unresolved.
If a filter supports a meeting or team process, include that purpose in its name. A teammate should be able to understand what it’s for without opening the query.
Maintain Filters as Work Changes
A saved filter can become stale when teams rename projects, change statuses, or adjust their workflow. Review important filters periodically, especially those used in dashboards or recurring meetings.
For example, a query that searches for a status called Open may stop matching work after a workflow change. A broader condition such as statusCategory != Done may suit some reviews better, though it can include more issue types and statuses.
Keep ownership clear for shared filters. If the person who created one changes roles, another team member may need to take responsibility for checking its query and access settings.
Jira Filter Management Solution: ONES.com
Jira filters help teams find and reuse issue searches. If your team is also reviewing how it manages project work, ONES.com offers a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

ONES Project may be worth evaluating when a team wants project workflows, planning, and reporting in a single project-management product. It supports Jira-compatible workflows, sprint management, custom workflows and fields, automation, and built-in reporting. These capabilities can help teams organize work without relying on as many added plugins, depending on their requirements.
Core capabilities
- Work scattered across project tools: ONES Project provides project-management capabilities in one product, helping teams bring issue tracking and planning into a shared work environment.
- Teams need familiar workflow patterns: Jira-compatible workflows can make it easier to assess a Jira alternative while keeping established ways of organizing work in view.
- Standard workflows don’t match team processes: Custom workflows let teams shape work stages around their process, so issue progression can reflect how work actually moves.
- Issue fields need more context: Custom fields allow teams to capture information relevant to their work, supporting more useful issue views and filtering.
- Teams plan work in time-boxed cycles: Sprint management supports planning and tracking sprint work, helping teams review what is active within a cycle.
- Repeated tasks take manual effort: Automation can handle suitable repetitive actions, reducing routine steps for teams that configure it for their workflows.
- Teams need progress visibility: Built-in reporting helps present project progress and work status without making additional reporting tools the starting point.
- Deployment requirements differ: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.
ONES.com offers a free plan for up to 30 seats. Teams can assess the product and deployment options against their security, operational, and collaboration requirements before deciding whether it fits.
Application scenarios
A software team reviewing Jira alternatives: The team can evaluate ONES Project’s workflows, sprint management, fields, and reporting against its current project processes. It should confirm that the product’s configuration matches its specific requirements before making a change.
An organization with restricted network requirements: A team that cannot use a cloud-only approach can review the On-Premise, Private Cloud, or Air-gapped deployment options, alongside the operational work required to manage its chosen environment.
A team connecting project work with internal knowledge: The team can consider ONES Project and ONES Wiki for project management and knowledge management, respectively. Since the products are sold separately, it can assess each one based on its own needs.
Common Challenges When Creating Jira Filters
- The filter returns no results: Check the project key, status spelling, issue type, and permissions. Remove one condition at a time to find what excludes the issues you expected.
- The filter returns too many issues: Add a relevant condition, such as a project, assignee, date range, or issue type. Review whether each condition narrows the search in a way that fits its purpose.
- A teammate cannot see the results: Review the filter’s sharing settings and confirm that the teammate can browse the project and view the relevant issues. Sharing a filter does not override issue permissions.
- A saved filter no longer matches team needs: Check whether the workflow, project configuration, or team process has changed. Update the query, test the results, and tell anyone who relies on the filter what changed.
- The JQL query produces an error: Confirm that field names and functions are supported in your Jira environment. Start with a simpler query, then add conditions one at a time.
FAQs About Jira Filters
Can I create a Jira filter without knowing JQL?
Yes. Use Jira’s basic issue search to choose fields such as project, status, assignee, and issue type. When the results look right, save the search as a filter. JQL is useful for more specific conditions, but you can create and reuse many everyday filters without writing it.
Why can’t someone else see my Jira filter?
The filter may still be private, or it may be shared with a different group or project role. The other person also needs permission to browse the project and view the issues. Check both the filter’s permissions and the project’s access settings before changing the query.
Can Jira filters show issues assigned to me automatically?
Yes. A query such as assignee = currentUser() AND resolution is EMPTY uses the person viewing the filter as the assignee value. That makes one saved filter useful for multiple people, as long as they have permission to see the matching issues.
Can I use a saved filter on a Jira dashboard?
Often, yes. A dashboard can use gadgets such as Filter Results, depending on your Jira setup and permissions. Select the saved filter in the gadget’s configuration, then check that the people viewing the dashboard can also access the filter and its issues.
Conclusion
Creating a Jira filter comes down to building a useful search, checking its results, saving it with a clear name, and setting the right access. Start with a practical example, such as unresolved bugs in one project, then adapt the query to your team’s fields and workflow.
A few careful checks can prevent empty results, confusing permissions, and filters that no longer reflect how work gets done. If your team is also assessing its project-management setup, compare its current process with options such as ONES Project and its deployment choices.