Create a Jira Filter: A Step-by-Step Guide for Beginners
Struggling to find Jira issues? Learn to create a filter in Jira, save and share it, and refine it with JQL. Click to discover.
Jira can show hundreds of issues at once, making the ticket you need surprisingly hard to find. Without a saved filter, you may repeat the same searches every morning or miss urgent work buried among completed tasks. That gets frustrating when a team depends on clear queues for sprint planning, support, or release checks. The fix is to build a focused Jira filter, save it, and set its sharing permissions carefully. You can start with simple fields and dropdowns, then use JQL when you need more control. I’ll walk you through both approaches, show you how to share and maintain a filter, and explain what to check when results look wrong. You’ll finish with a practical filter you can reuse instead of rebuilding your search each time.
But here's the truth: a useful filter is more than a search. It is a repeatable view of the work your team needs to act on.
How to Create and Save a Jira Filter
You can create a Jira filter by searching for issues, refining the results, and saving the search. The Basic search screen is easiest for beginners; Advanced search lets you write JQL for precise conditions.
Open issue search. In Jira, open the issue search area. Depending on your Jira version and navigation, look under Filters or use the search option in the top navigation.
Choose Basic search to get started. Basic search lets you select fields such as project, status, assignee, and issue type from menus. Use Advanced search if you already know JQL or need conditions the menus cannot express.
Add conditions that match your goal. For example, select the Support project, choose an open status, and set the assignee to yourself. Each condition narrows the results, so start with only the criteria you need.
Review the results. Check several returned issues to confirm that they belong in the view. If an expected issue is missing, inspect the project, status, and assignee conditions before adding more complexity.
Save the search. Select Save as or Save filter, enter a clear name, and confirm. A name like “My Open Support Issues” is more useful than “Filter 1.”
Set sharing permissions if needed. Open the filter’s details or management options and choose who can view it. Sharing options depend on your Jira permissions and configuration. Give access only to the people or groups who need the filter.
Find and reuse the filter. Saved filters usually appear in a filter list or under favorites. Star a frequently used filter if Jira offers that option in your view.
Here’s why: saving preserves the search criteria, so you can return to the same view without recreating each condition. The issues shown can change as people update their work, but the filter’s rules remain in place.

Try a Simple JQL Filter
JQL, or Jira Query Language, lets you describe the issues you want with a short query. In Advanced search, try this example and replace SUPPORT with your project key:
project = SUPPORT AND statusCategory != Done ORDER BY priority DESC
This query returns issues in the SUPPORT project that are not in the Done status category, then sorts higher-priority issues first. Run it, inspect the results, and save it with a clear name.
Choose the Right Search Method
Basic search works well when your conditions fit Jira’s menus. It is a good starting point for a personal queue, such as issues assigned to you that are still open. You can add a project or issue type without learning query syntax.
Advanced search is useful when you need more control. For example, JQL can combine conditions with AND and OR, sort results, or find work updated within a certain period. Consider this example:
project = SUPPORT AND assignee = currentUser() AND updated >= -7d ORDER BY updated DESC
It shows issues in the SUPPORT project assigned to the current user, updated within the past seven days, with the most recently updated issues first. The best part? You can begin with Basic search and switch to Advanced search as your needs grow.
Understand the Building Blocks
Fields: Properties such as project, status, priority, assignee, and created date.
Operators: Comparisons such as =, !=, IN, and >=.
Values: The project, status, person, or date you want Jira to match.
Logic: AND narrows results by requiring multiple conditions. OR includes issues that meet either condition.
Sorting: ORDER BY controls the order, such as placing the highest-priority issues first.
Let me explain: a filter returns the issues that satisfy its conditions. If a query combines several rules, one overly restrictive condition can remove issues you expected to see.
Write a Filter That Answers One Clear Question
Before adding conditions, state the question your filter should answer. “What should I work on next?” is a better starting point than “Show me everything about the project.” It gives you a practical way to decide which fields matter.
For a sprint planning view, you might use a project, an active sprint, and a status condition. For a weekly support review, you could focus on unresolved issues created during the past seven days. A filter for release checks may include a version field and a status that is not complete.
Example: Find Your Open Work
Use this query to find unresolved issues assigned to you:
assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC
The currentUser() function means each person who opens the filter sees their own assigned issues, subject to Jira access. This can make a shared team filter more reusable than one that names a single person.
Example: Track Recently Created Support Issues
Use this query to review recent work in a project:
project = SUPPORT AND created >= -7d ORDER BY created DESC
It includes issues created in the past seven days and puts the newest near the top. If you only want unfinished work, add a status condition that matches your team’s Jira setup.
You might be wondering: should you add every helpful condition now? Usually, no. Start with the smallest query that answers the question, then add one condition at a time and check how the results change.
Share, Organize, and Maintain Saved Filters
A saved filter can remain private or be shared with other people, groups, or project roles when your Jira permissions allow it. Sharing helps a team use the same view, but a filter does not automatically grant access to the issues it finds. Each person still needs permission to view those issues.
Give filters names that describe their purpose and scope. “Unresolved Bugs in Mobile” communicates more than “Bugs.” If you create several views, use a consistent naming pattern, such as “Support — New This Week” and “Support — Assigned to Me.”
Check Sharing Before You Send a Link
Open the saved filter’s details and review its access settings before sharing it. A teammate may be able to open the filter but see fewer results because project permissions differ. If someone reports an empty view, check both the filter’s sharing settings and their access to the relevant project.
Keep Filters Useful Over Time
Review saved filters when a project changes its workflow, status names, or team structure. A filter that depends on a former team member’s account may stop serving its original purpose. Update the conditions, revise its name, or remove it if the team no longer needs it.
For example, if your team replaces “In Review” with “Ready for Review,” a filter using the old status may stop returning the expected issues. A quick check after workflow changes prevents that surprise.
Common Jira Filter Problems and Fixes
The filter returns no issues. Check the project key, spelling of field values, and whether every condition must be true. Remove one condition temporarily to see which rule excludes the expected issue.
Some teammates see different results. Jira access can vary by person. Confirm that each teammate can view the project and issues, then review the filter’s sharing permissions.
The query gives an error. Verify field names, operators, quotation marks, and parentheses. Try the query in smaller pieces, then add conditions one at a time.
The filter becomes hard to maintain. Remove conditions that do not support the filter’s main purpose. Give the remaining rules and filter name a quick review when team workflows change.
But here's the truth: many filter problems come from one small mismatch, such as a changed status name or a missing permission. Testing each condition separately is often faster than rewriting the entire query.
Jira Filter Solution: ONES.com

Value Proposition
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so you can consider ONES Project when you want a Jira alternative without adopting the full platform.
Core Capabilities
Issue views are difficult to organize: ONES Project supports custom workflows and fields, helping teams shape issue tracking around their work and create more relevant views.
Your team needs familiar project processes: Jira-compatible workflows can make it easier to carry over established practices when evaluating a Jira alternative.
Sprint planning needs a clear home: Sprint management supports teams that plan and track work in iterations.
Teams repeat the same administrative actions: Automation can reduce manual steps for routine project tasks.
Progress is hard to communicate: Built-in reporting gives teams reporting capabilities within the project management environment.
Too many add-ons complicate the setup: Native capabilities can reduce reliance on plugins for supported project needs.
Hosting requirements are strict: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
Self-hosting may mean feature trade-offs: ONES.com states that its cloud and self-hosted versions have full feature parity, giving teams deployment flexibility without a planned feature gap.
Application Scenarios
A Jira team reviewing alternatives: A team that relies on custom workflows, sprint planning, and reporting can evaluate ONES Project as a Jira alternative. It can compare how existing practices fit while considering native capabilities and plugin requirements.
A team with restricted network requirements: An organization that cannot use a public cloud service can assess On-Premise, Private Cloud, or Air-gapped deployment options. Its technical team can compare deployment needs and feature expectations during evaluation.
A project group connecting work and team knowledge: A team may use ONES Project for project management and ONES Wiki for knowledge management. Since the products are sold separately, the team can choose the product or products that suit its needs.
ONES.com is worth evaluating when your needs extend beyond creating Jira filters. If your immediate goal is simply to find and save Jira issues, start with Jira’s built-in search and filter controls.
Frequently Asked Questions
Can I create a Jira filter without knowing JQL?
Yes. Start with Basic search and choose conditions from the available menus, such as project, status, or assignee. When the results look right, save the search as a filter. You can learn JQL later if you need more complex logic, sorting, or date conditions. Basic search is enough for many everyday views, including a personal list of open issues.
What is the difference between a Jira search and a saved filter?
A search is the set of conditions you run to find issues. Saving that search creates a filter you can name and return to later. The saved filter keeps its criteria, while the issues in its results may change as work is created or updated. You can also share a saved filter when your Jira permissions allow it.
Why can a teammate not see all the issues in my filter?
Sharing a filter does not necessarily give someone permission to view every issue it finds. Their project and issue permissions still apply, and their access may differ from yours. Check whether the filter is shared with them or their group, then confirm they can access the relevant project. If results remain different, compare the exact conditions and account-specific values.
How do I make a Jira filter show only my issues?
In Basic search, set the assignee field to yourself. In JQL, use assignee = currentUser(), then add a status or project condition if needed. For example, assignee = currentUser() AND resolution = Unresolved finds unresolved issues assigned to the person running the query. Save the search if you expect to reuse it.
Conclusion
To create a Jira filter, search for the issues you need, confirm the results, and save the conditions with a clear name. Use Basic search for straightforward views and JQL when you need more precise logic. Set sharing permissions deliberately, and review filters when project workflows change.
Filters can make Jira easier to navigate, but a confusing query or access mismatch can bring the frustration back. Start with one clear question, build the smallest useful search, and refine it only after checking the results. That gives you a dependable view of the work that matters.