How to Create a Jira Filter: Step-by-Step Guide for Teams

Need faster Jira searches? Learn how to use jira create filter to save, refine, and share team views. Click to discover!

Finding the right Jira issues should take seconds, yet many teams still scroll through crowded project views, repeat the same searches, and miss important work. A poorly saved search can hide blocked tasks, overdue work, or sprint risks until they become expensive problems. The frustration grows when every teammate builds a slightly different query for the same question. The solution is simple: create a Jira filter, give it a clear purpose, and share it with the people who need it. This guide shows you how to build, save, refine, share, and manage filters for everyday team workflows. You’ll also see practical JQL examples that help turn a basic search into a reliable working view.

How to Create a Jira Filter

A Jira filter is a saved search that displays issues matching specific conditions. You can build one with Jira’s visual search options or write Jira Query Language, commonly called JQL, for more precise results.

Here’s why: a useful filter does more than locate issues once. It gives your team a repeatable view of assigned work, upcoming deadlines, unresolved defects, sprint progress, or operational risks.

Jira product screenshot

1. Open the issue search screen

Sign in to Jira and open the issue search area. Depending on your Jira version, you may find it under Issues, Search for issues, or a similar navigation option.

You’ll usually see two search modes:

Basic search: Choose fields such as project, issue type, status, assignee, priority, and labels.
Advanced search: Write a JQL query when you need more control.

Start with Basic search if you are learning Jira. Switch to Advanced search when the visual controls cannot express the conditions you need.

2. Define the purpose before adding conditions

Decide what the filter should help someone do. A clear purpose prevents a query from becoming a long collection of unrelated conditions.

For example, “show my urgent work” is more useful than “show everything in the project.” The first question leads to practical criteria such as assignee, priority, and status.

Common filter purposes include:

Showing open issues assigned to you.
Finding high-priority defects that remain unresolved.
Reviewing work planned for the current sprint.
Monitoring issues without an assignee.
Listing tasks due within the next two weeks.
Checking recently updated work during a stand-up.

3. Build the search with Basic mode

Choose the project first if your search applies to one project. Then add the fields that narrow the result to the work you actually want to see.

For example, a personal work queue might use:

Project: Product Website
Assignee: Current user
Status: To Do or In Progress
Priority: High or Highest

Jira updates the results as you add conditions. Review the issue count after each major change. If the list becomes empty, remove the most recent condition and check whether its value matches your workflow.

4. Switch to Advanced mode when needed

Basic search works well for straightforward conditions. Advanced mode becomes more useful when you need date functions, multiple projects, linked conditions, or carefully grouped logic.

Try this query to find unresolved high-priority work assigned to you:

assignee = currentUser()
AND priority in (Highest, High)
AND resolution is EMPTY
ORDER BY updated DESC

The query combines three ideas. It identifies the person, excludes completed issues, and places recently updated work near the top.

5. Add ordering to make the results practical

Filtering determines which issues appear. Ordering determines which issue appears first.

Without an ORDER BY clause, results may not appear in the sequence your team expects. Add an ordering rule that supports the task.

Examples include:

ORDER BY priority DESC, updated DESC for urgent review queues.
ORDER BY duedate ASC for deadline monitoring.
ORDER BY status ASC, rank ASC for sprint planning.
ORDER BY created DESC for newly submitted requests.

Use fields your Jira setup supports. Some teams use custom fields or ranking behavior that changes the most useful ordering.

6. Test the results before saving

Read several results instead of checking only the total count. A filter can return the expected number while still including the wrong issue types or excluding important work.

Ask yourself:

Does every displayed issue belong in this view?
Are any important issues missing?
Will the results remain useful next week?
Can another teammate understand the purpose quickly?

For example, a filter for unresolved bugs may accidentally include improvement requests if the issue type condition is missing. Add issuetype = Bug when the distinction matters.

7. Save the filter with a clear name

Select Save as, then use a name that explains the audience and purpose. Good names are specific without becoming long.

Useful examples include:

My High-Priority Open Work
Unassigned Production Bugs
Current Sprint Risks
Customer Requests Due Soon
Recently Updated Support Issues

Avoid names such as “My Filter” or “Test Search.” Those labels become confusing when a team has dozens of saved searches.

8. Share the filter when collaboration requires it

A saved filter is usually private until you share it. Open the filter’s details or manage-filters area, then choose the relevant sharing option.

You may be able to share it with a project, group, role, or selected people. Choose the narrowest audience that supports the workflow.

For example, a product team may share a sprint-risk filter with its project role. A personal work queue should usually remain private.

9. Add the filter to a dashboard or board

A filter becomes more valuable when people can reach it without rebuilding the search. You can use saved filters in dashboard gadgets, boards, subscriptions, and other Jira views.

For a daily team dashboard, consider adding:

Unresolved high-priority issues.
Issues without an assignee.
Work updated during the last seven days.
Items approaching their due date.

Keep each dashboard focused. Ten competing gadgets can make an important warning harder to notice.

10. Review and maintain the filter

Workflows change. Projects gain new statuses, teams rename priorities, and custom fields evolve. Review important filters whenever your process changes.

Open the filter occasionally and confirm that it still returns useful results. Remove outdated conditions, update names, and check sharing permissions after team changes.

JQL Examples for Everyday Jira Filters

JQL gives you a precise way to describe the work you want to see. You do not need to memorize every function. Start with fields your team already uses, then add operators such as =, in, is EMPTY, and date functions.

My open work

assignee = currentUser()
AND resolution is EMPTY
ORDER BY priority DESC, updated DESC

This view is useful for personal planning because it removes resolved issues and places higher-priority work first.

Unassigned issues

project = WEB
AND assignee is EMPTY
AND resolution is EMPTY
ORDER BY created ASC

This filter helps team leads find work that has entered the queue without an owner. Ordering by creation date highlights items waiting longest.

Current sprint issues

project = WEB
AND sprint in openSprints()
ORDER BY rank ASC

Use this view during stand-ups or sprint reviews. The exact sprint functions available may depend on your Jira configuration.

Overdue work

duedate < now()
AND resolution is EMPTY
ORDER BY duedate ASC

Overdue filters should normally exclude resolved issues. Otherwise, completed work can create noise in the results.

Open production defects

project = WEB
AND issuetype = Bug
AND priority in (Highest, High)
AND resolution is EMPTY
AND labels = production
ORDER BY priority DESC, created ASC

This example combines project, issue type, priority, resolution, and label. It works well for a defect triage queue when the team consistently applies the label.

How to Make Filters Easier for Teams to Use

The best filters answer one recurring question. A product manager may need “what threatens this release?” A developer may need “what should I work on next?” A support lead may need “which customer issues have no owner?”

Let me explain: the same project can need several filters because each role makes different decisions. One broad search rarely serves everyone well.

Use predictable naming

Put the main purpose near the beginning of the name. For example, “Release 4.2 — Open High-Priority Bugs” is easier to scan than “Bugs Filter Final Version.”

Keep conditions understandable

A complex query may be powerful, but complexity creates maintenance risk. If a filter needs a paragraph of explanation, consider splitting it into two focused views.

Use team conventions

Agree on how your team uses labels, components, issue types, and priorities. A filter depends on consistent issue details.

For example, if only some engineers add the customer-blocked label, a filter using that label will not show every blocked issue. The process must support the query.

Choose sharing permissions carefully

Sharing a filter makes collaboration easier, but broad sharing can clutter menus and expose views to people who do not need them. Keep personal filters private and publish team views deliberately.

Common Jira Filter Problems and Fixes

Most filter problems come from one of three causes: incorrect logic, inconsistent issue details, or outdated permissions. Check the query first, then inspect the issues themselves.

Problem	Likely cause	Practical fix
The filter returns no issues	A condition is too narrow or uses a value that does not exist	Remove the latest condition, check field values, and add conditions one at a time
Too many issues appear	The query lacks project, status, issue type, or resolution criteria	Add a condition that matches the decision the filter should support
Teammates cannot find the filter	The filter is private or shared with the wrong group	Review permissions and share it with the correct project role or group
Completed work still appears	The query does not exclude resolved issues	Add `resolution is EMPTY` or use the appropriate unresolved condition
Results look inconsistent	People use labels, priorities, or issue types differently	Agree on field usage and clean up older issue details

Jira Filter Solution: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com combines project management and knowledge management in one platform, powered by ONES Assistant. ONES Project is a Jira alternative that supports structured issue work, reporting, and configurable workflows without requiring a separate tool for every team need.

Teams can use ONES Project separately, or pair it with ONES Wiki for knowledge management. Both are sold separately, so you can choose the capability that fits your workflow.

Core Capabilities

Scattered project views → Custom filters and fields → Teams can shape work views around project roles, priorities, stages, and operational needs.
Complex workflow changes → Configurable workflows → Administrators can reflect approval paths, review stages, and delivery processes without forcing every team into one default flow.
Limited sprint visibility → Sprint management → Teams can plan iterations, review progress, and connect daily work with sprint goals.
Manual recurring actions → Automation → Repetitive transitions and notifications can follow defined rules, reducing routine handling.
Unclear progress → Built-in reporting → Native reports help teams examine delivery movement, workload, and project trends without relying on a long chain of add-ons.
Plugin-heavy Jira environments → Native feature parity → Jira-compatible workflows and built-in capabilities can reduce dependence on multiple plugins for common project operations.
Restricted hosting requirements → On-premise, private cloud, and air-gapped deployments → Organizations can select a deployment model that matches security, compliance, and network constraints.
Different hosting expectations → Four deployment choices → Cloud, On-Premise, Private Cloud, and Air-gapped options give teams more control over how the platform runs.
Separate project and knowledge work → ONES Project plus ONES Wiki → Teams can connect delivery work with internal guidance, procedures, and product knowledge when both products are appropriate.
Growing adoption costs → Free plan for up to 30 seats → Smaller teams can begin with a limited group before deciding whether broader adoption fits their needs.

Application Scenarios

Software delivery team: A development group can replace scattered Jira views with project filters for sprint work, unresolved defects, blocked items, and release readiness. Custom workflows can reflect code review, testing, approval, and deployment stages.

Regulated organization: A company with restricted network requirements can run project management in an air-gapped or on-premise environment. Full feature parity between cloud and self-hosted versions helps teams keep a familiar working model.

Cross-functional product group: Product, engineering, and support teams can manage delivery in ONES Project while maintaining guidance in ONES Wiki. This arrangement keeps operational work and team knowledge connected without forcing both products into one purchase.

Common Challenges When Creating Jira Filters

Challenge: The query reflects a vague goal

Problem: A filter called “Important Issues” may use inconsistent priorities or include too many issue types.

Solution: Define the decision first. Change the goal to “high-priority unresolved production bugs” and add conditions that match that precise need.

Challenge: Filter logic becomes difficult to read

Problem: Long combinations of AND and OR can produce unexpected results.

Solution: Use parentheses where grouping matters. Test each section separately before combining the clauses.

Challenge: Team members use fields differently

Problem: One person marks an issue as blocked with a label, while another changes its status. A single filter cannot reliably detect both behaviors.

Solution: Agree on one primary signal for each important condition, then update older issues to follow that convention.

Challenge: Shared filters become outdated

Problem: A project changes its statuses or releases, but old filters continue using retired values.

Solution: Assign ownership to a team lead or project administrator. Review shared filters during retrospectives or workflow changes.

FAQs

Can I create a Jira filter without knowing JQL?

Yes. Jira’s Basic search lets you choose common fields through menus. You can create, test, and save a useful filter without writing code-like syntax. Move to Advanced search when you need functions, complex grouping, multiple projects, or date-based conditions.

Why can’t my teammate see my saved filter?

New filters are often private. Open the filter’s details and review its sharing settings. Choose the correct project, group, role, or individual access option. Also confirm that your teammate has permission to view the related project and issues.

What should I name a shared filter?

Use a name that explains the purpose and audience. “Support — Unassigned High-Priority Requests” is clearer than “Support Filter.” If the view applies to a sprint or release, include that context. Avoid names such as “New,” “Final,” or “Test,” which lose meaning quickly.

How do I exclude completed issues?

Many workflows use resolution is EMPTY to identify unresolved issues. You can also use a status category or specific status values, depending on your Jira setup. Test the results because teams may configure completion statuses differently.

Can one filter cover several projects?

Yes. Use a project condition with multiple values, such as project in (APP, WEB, MOBILE), if your permissions allow access. Make sure the projects use compatible issue types, statuses, and fields. Otherwise, the combined results may be difficult to interpret.

How often should a team review its filters?

Review important shared filters whenever the workflow, team structure, release plan, or field conventions change. A quarterly check can also help. Look for retired values, unexpected results, outdated names, and sharing permissions that no longer match the team.

Conclusion

Creating a Jira filter starts with a clear question, such as “What urgent work needs attention?” Build the search around that question, test the results, add useful ordering, and save it with a descriptive name.

But here’s the truth: a filter remains valuable only when your team uses fields consistently and reviews shared views over time. A precise query cannot correct incomplete labels, unclear priorities, or outdated workflow values.

When you need a Jira alternative, ONES Project offers Jira-compatible workflows, custom fields, sprint management, automation, reporting, and deployment choices that include cloud, on-premise, private cloud, and air-gapped environments. The right platform should make important work easier to find, understand, and act on.