How to Create a Jira Filter: 7 Steps for Better Searches

Need better Jira searches? Learn how to use jira create a filter in 7 steps with JQL. Read now to find issues faster!

Jira searches can become frustrating when the same issues take several minutes to find every time. You may remember part of a ticket title, a project key, or a status, yet still end up scanning an overcrowded results page.

That wasted effort grows when your team repeats the same search across sprints, releases, support queues, or bug reviews. A small search mistake can also hide important work or show irrelevant tickets.

But here's the truth: Jira lets you turn a useful search into a reusable filter. I’ll show you how to create one in seven practical steps, refine it with JQL, share it safely, and keep it useful as your project changes.

How to Create a Jira Filter in 7 Steps

A Jira filter is a saved search that returns issues matching specific conditions. You can build it with Jira’s visual search options or write a JQL query when you need more control.

The fastest route is simple: open issue search, add conditions, review the results, switch to JQL when needed, save the search, name it clearly, and configure access.

Open Jira issue search. Select Issues in the top navigation, then choose Search for issues. Depending on your Jira version, this area may appear under Filters or View all issues and filters.

You should see a search screen with fields for project, status, assignee, priority, type, labels, and other available criteria.
Choose the basic or advanced search mode. Basic search works well when you want a quick combination of standard fields. For example, you might select one project, set the status to In Progress, and choose yourself as the assignee.

Advanced search uses JQL, Jira’s query language. Select Advanced when you need conditions such as date ranges, multiple projects, empty fields, or linked logic.
Add conditions that match your purpose. Start with the smallest useful set of criteria. A release review may need a project, fix version, and unresolved status. A personal work queue may need your assignee name and active statuses.

For example, a basic search could return open bugs in a mobile project. Avoid adding every available field at once, because excessive conditions make a filter hard to understand and maintain.
Refine the search with JQL when necessary. A query such as the following finds unresolved high-priority issues in a project:

project = APP AND priority = High AND resolution IS EMPTY ORDER BY updated DESC

IS EMPTY helps locate issues without a resolution. The ordering clause places recently updated work near the top.
Run the search and inspect the results. Select Search or Run, then check whether every result belongs in the intended work queue. Test the query with a few known issues.

If an expected issue is missing, review spelling, project keys, status names, date boundaries, and permission limits. A technically valid query can still be too narrow.
Save the search as a filter. Select Save as, enter a descriptive name, and confirm the save action. Use a name that explains both the content and the purpose.

APP — Unresolved High-Priority Bugs is clearer than My Filter 2. Good names help you and your teammates recognize the right search later.
Set sharing, favorites, and optional subscriptions. Open the filter details or manage-filters area to add it to your favorites. If teammates need it, share it with the right project role, group, or team.

You can also configure an email subscription when Jira permissions and your plan allow it. Review access carefully before sharing sensitive work, customer details, security findings, or internal planning issues.

Jira product screenshot

Example JQL for a Practical Team Filter

Suppose your team wants a view of unresolved bugs assigned to the current user. This query is a useful starting point:

issuetype = Bug AND assignee = currentUser() AND resolution IS EMPTY ORDER BY priority DESC, updated DESC

The query filters by issue type, limits results to your own work, excludes resolved issues, and sorts urgent work first. You can replace currentUser() with a specific account when creating a shared team view.

Check the Query Before You Share It

Run the search while thinking like another person who will use it. Ask whether the results remain useful when the sprint changes, a new assignee joins, or another release begins.

Here's why: a filter that depends on your personal name may be perfect for your queue but unsuitable for a team dashboard. A shared filter often works better with project roles, labels, components, or current sprint functions.

Choose the Right Search Method

Jira gives you two main ways to build a filter. Basic search is visual and accessible, while advanced search gives you the precision of JQL.

Search method	Best use	Example
Basic search	Quick searches using standard fields	Find bugs in one project with a specific status
Advanced JQL	Complex logic, date conditions, and reusable team views	Find unresolved work updated during the last seven days
Saved filter	Repeated searches and dashboard gadgets	Track open release blockers every morning
Filter subscription	Scheduled email summaries	Send unresolved priority issues to a project group

You might be wondering: should you always use JQL? No. Start with basic search when it answers the question quickly. Move to JQL when the visual controls cannot express the logic clearly.

For example, searching for issues in one project is straightforward through the basic interface. Combining two projects, excluding a label, checking a date window, and sorting by priority is usually easier in JQL.

Write Jira Filters That Stay Useful

A saved filter should answer one recurring question. Before saving it, complete this sentence: “I use this search to see…”

Unresolved bugs blocking the next release.
Work assigned to me that has not changed recently.
Stories planned for the current sprint.
High-priority support issues without an owner.

That sentence gives your filter a clear boundary. If you cannot explain its purpose, the search probably combines too many unrelated needs.

Use Stable Conditions

Some criteria stay useful over time, such as issue type, resolution status, priority, component, and project. Other criteria become outdated quickly, including a specific sprint name or temporary label.

For instance, project = APP AND resolution IS EMPTY may remain useful for months. A query that names Sprint 18 will become stale as soon as the sprint ends.

Use Relative Dates for Recurring Reviews

Relative date functions help a recurring filter update automatically. A query such as updated >= -7d finds issues updated during the previous seven days.

This works better for a weekly review than a fixed date. A fixed date eventually stops matching new work, while a relative date moves with the calendar.

Keep Sorting Intentional

Sorting determines what people see first. For an urgent queue, try ORDER BY priority DESC, updated DESC. For a planning view, ranking by rank or due date may make more sense.

The best part? A small ordering decision can make a filter feel much more useful without changing its conditions.

Common JQL Patterns for Better Searches

JQL becomes easier when you recognize a few reusable patterns. Each one answers a common project question.

Find Unresolved Issues

Use resolution IS EMPTY when you want issues that remain open from a resolution perspective:

project = APP AND resolution IS EMPTY

This may include issues in several active statuses. If your workflow has unusual statuses, confirm that the results match your team’s definition of unfinished work.

Find Work Assigned to You

Use assignee = currentUser() for a personal work queue:

assignee = currentUser() AND statusCategory != Done

The status category condition is often more portable than listing every active status separately. It can reduce maintenance when a team adds another in-progress status.

Find Issues Without an Assignee

Unassigned work can disappear during handoffs. Use:

project = APP AND assignee IS EMPTY AND resolution IS EMPTY

This is useful before sprint planning, triage meetings, and release readiness reviews.

Find Recently Updated Issues

For a short activity review, use:

project = APP AND updated >= -14d ORDER BY updated DESC

Change -14d to -7d or another period that fits your review rhythm. A shorter period keeps the results focused.

Find Issues in the Current Sprint

Teams using active sprint planning can try:

sprint in openSprints() AND resolution IS EMPTY

Whether this works exactly as expected depends on your Jira configuration and board setup. Always test it against a known sprint.

Manage Sharing, Permissions, and Filter Ownership

Saving a filter does not automatically make it available to everyone. Jira permissions determine who can view, edit, or manage the saved search.

A personal filter should usually remain private. A team filter may be shared with a project role or group. A department-wide search may need broader access, but wider visibility increases the chance of exposing restricted issue details.

Let me explain: sharing controls usually affect the filter and its results together. Someone may see the filter name but still receive fewer results if their Jira permissions do not allow access to certain issues.

Use Clear Ownership

A filter becomes harder to maintain when its owner leaves the project or changes teams. For important operational views, agree on an owner or maintenance routine.

Review shared filters during project changes. Remove duplicates, update outdated queries, and rename unclear searches before they become part of a team’s daily routine.

Protect Sensitive Searches

Security findings, customer-impacting incidents, hiring tasks, and financial planning may require restricted access. Do not share a filter broadly simply because the query itself looks harmless.

Check the issue permissions behind the search, then test the result with an account that reflects the intended audience.

Use Saved Filters Across Jira Workflows

A filter becomes more valuable when it appears where your team already works. You can often use saved searches in dashboards, boards, reports, and email subscriptions.

Dashboards

Add a saved filter to a dashboard gadget to show issues such as open blockers, overdue work, or recently created bugs. A release manager might use three filters: blockers, unresolved high-priority issues, and work without owners.

Boards and Backlogs

Many Jira boards use a filter to determine which issues appear. A board query should be broad enough to include the team’s working scope, while quick personal filters can remain narrow.

Changing a board filter can affect every person who relies on that board. Treat board queries as shared workflow settings rather than personal experiments.

Backlog product screenshot

Reports and Subscriptions

Saved searches can support recurring reports and email summaries. A support team might receive unresolved urgent tickets each morning, while an engineering lead reviews issues untouched for two weeks.

Before enabling notifications, choose a sensible schedule. Too many emails cause people to ignore useful alerts.

Natural Jira Filter Solution: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com brings project management and knowledge management into one platform. ONES Project provides Jira-compatible workflows with built-in reporting, custom fields, sprint management, and automation.

It can suit teams that want a Jira alternative with native capabilities, fewer plugin dependencies, and deployment choices that include on-premise and air-gapped environments.

Core Capabilities

Scattered search needs → Unified project views → Faster work discovery

When project information sits across disconnected tools, finding the current status takes extra effort. ONES Project combines project views, issue details, sprint activity, and reporting in one workspace.

The result is a clearer route from a work request to its owner, status, priority, and delivery context.

Complex Jira queries → Custom workflows and fields → More precise tracking

Teams often create increasingly complicated searches because standard fields do not reflect their process. ONES Project supports custom workflows and custom fields for different project requirements.

You can represent stages such as technical review, security approval, customer validation, or release readiness without forcing every team into one workflow.

Manual sprint coordination → Sprint management → Better planning visibility

When sprint information is spread across separate views, planning conversations can drift away from actual work. Sprint management capabilities keep planned items, active work, and completed items connected.

Teams can review sprint progress with less manual reconciliation.

Plugin-heavy automation → Built-in automation → Fewer moving parts

Additional plugins can create maintenance work, separate settings, and inconsistent behavior. ONES Project includes automation options for recurring project actions.

That can reduce the number of external additions required for assignments, transitions, notifications, or routine updates.

Limited reporting flexibility → Built-in reporting → More useful project reviews

A saved search shows matching issues, but leaders often need trends, workload views, and progress summaries. ONES Project includes built-in reporting for project monitoring and review meetings.

Teams can move from a narrow task list to a broader view of delivery health.

Cloud-only constraints → Four deployment choices → Better environment fit

Some organizations cannot place project work in a public cloud. ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments.

The self-hosted versions provide feature parity with the cloud version, helping teams choose an environment without giving up core project capabilities.

Separate project and knowledge work → ONES Project plus ONES Wiki → Connected delivery context

Project tasks often depend on requirements, decisions, procedures, and technical guidance. ONES Wiki provides knowledge management capabilities alongside ONES Project.

They are sold separately, so teams can adopt the project or knowledge product according to their needs.

Jira migration concerns → Jira-compatible workflows → A more familiar transition

Teams considering a Jira alternative may worry about rebuilding established ways of working. ONES Project supports Jira-compatible workflows, which can make process mapping more familiar.

You should still review fields, permissions, integrations, reports, and team habits before planning a transition.

Application Scenarios

Software release team: A development group can manage stories, bugs, sprints, release work, and reporting in ONES Project. Custom fields can capture risk level, release train, and approval state.

Restricted-network engineering: An organization with strict network controls can evaluate an air-gapped deployment. The team can retain project management capabilities inside its required environment.

Product and engineering collaboration: A product group can use ONES Project for delivery tracking and ONES Wiki for requirements, decisions, and internal guidance. The two products can support a connected workflow while remaining separately sold.

Common Challenges When Creating Jira Filters

The filter returns too many issues

Problem: Your query uses only a project or broad status, so the result list becomes difficult to scan.

Solution: Add one meaningful condition, such as issue type, priority, component, assignee, or resolution. Then rerun the search and confirm that the list answers one specific question.

The filter misses expected issues

Problem: A status, date condition, permission rule, or spelling difference excludes relevant work.

Solution: Test each condition separately. Start with the project, add the issue type, then add status and date limits. This reveals which condition removes the expected result.

The query becomes outdated

Problem: The filter names a sprint, temporary label, or individual who no longer owns the work.

Solution: Replace fixed values with relative dates, project roles, current-user functions, or stable workflow fields where appropriate. Schedule a periodic filter review.

Teammates cannot see the results

Problem: The filter is private, the sharing setting is too narrow, or issue permissions restrict visibility.

Solution: Review filter sharing and project permissions together. Ask a teammate in the intended audience to test the filter before relying on it for a meeting or report.

Too many similar filters exist

Problem: Several searches have unclear names and slightly different conditions.

Solution: Keep one authoritative version for each recurring purpose. Add a naming convention such as project, purpose, and audience: APP — Release Blockers — Team.

FAQs About Jira Filters

What is the difference between a Jira search and a filter?

A Jira search is the query you run to find issues. A filter is that search after you save it for repeated use. You can reuse a saved filter in dashboards, boards, reports, and subscriptions, depending on your permissions and Jira configuration. A temporary search helps with a one-time question, while a saved filter supports a recurring workflow.

Can I create a Jira filter without knowing JQL?

Yes. Jira’s basic search lets you choose common fields through a visual interface. You can select a project, status, assignee, priority, issue type, and other options without writing code. When the search becomes more complex, switch to advanced mode and refine the generated query with JQL.

Why can’t my teammate see my saved filter?

Your filter may be private or shared with a group, project role, or team that does not include your teammate. Issue permissions can also limit the results. Open the filter’s sharing settings and confirm the project access behind the search. Test the filter with someone who has the intended permission level.

How do I edit an existing Jira filter?

Open the saved filter, change the search conditions, and run the updated query. Then select the save option to preserve the changes. If you do not own the filter, Jira may prevent editing or let you save a separate copy. Use a clear name when creating a revised version.

Can a Jira filter update automatically?

Yes. Filters recalculate when you open or use them, so conditions such as updated >= -7d move with time. You can also use functions such as currentUser() or sprint functions when your Jira setup supports them. Check the results regularly because workflow changes can affect the query’s meaning.

How many conditions should a useful filter contain?

There is no ideal number for every situation. A personal queue may need two or three conditions, while a release review may require several. Focus on purpose rather than quantity. If teammates cannot explain why each condition exists, simplify the filter or divide it into separate searches.

Conclusion

Creating a Jira filter takes seven practical actions: open issue search, choose a search mode, add conditions, refine with JQL, inspect results, save the search, and manage access.

Start with one recurring question, use stable criteria, test the results, and name the filter clearly. Relative dates, current-user functions, intentional sorting, and careful sharing can make saved searches far more useful.

But here's the truth: a filter only helps when it reflects the way your team actually works. If Jira searches become difficult to maintain, a platform such as ONES.com may offer a broader Jira alternative with compatible workflows, built-in reporting, custom fields, sprint management, automation, and flexible deployment options.