How to Create a Jira Filter: A Step-by-Step Guide [2026]

Need to create filter jira views faster? Follow this step-by-step guide to master JQL, permissions, and sharing. Click to discover the 2026 method!

Finding the right Jira issue can become frustrating when every search starts from scratch. A small task list can quickly turn into dozens of clicks, missed filters, and outdated results.

That friction grows when your team needs the same view for sprint planning, bug triage, release tracking, or executive reporting. One incorrect condition can hide important work or flood your screen with irrelevant issues.

But here's the truth: creating a Jira filter is straightforward once you understand the search fields, JQL, permissions, and sharing options. This guide shows you how to build, save, share, edit, and troubleshoot filters in Jira.

How to Create a Jira Filter

A Jira filter is a saved search that displays issues matching selected conditions. You can create one with Jira’s visual search, write a JQL query, save it, and share it with approved people or groups.

The quickest method is to open issue search, add conditions such as project, status, assignee, or priority, then select Save as. You can use the visual builder for simple searches or switch to JQL for precise control.

Jira product screenshot

Step 1: Open the Issue Search Screen

Sign in to Jira.
Open Filters in the top navigation.
Select View all issues or Search for issues.
Choose the project or issue area you want to search.

Jira’s labels vary slightly between Cloud and self-managed deployments. Look for the issue search page if the menu wording differs.

Step 2: Choose Basic or Advanced Search

Jira usually offers two search modes. Basic search uses menus and fields, while Advanced search uses Jira Query Language, commonly called JQL.

Basic search works well when you need a quick view, such as open bugs in one project. Advanced search helps when you need conditions involving dates, functions, custom fields, or several projects.

Step 3: Add Search Conditions

Start with the narrowest useful condition. For example, select one project before adding status, assignee, sprint, or priority.

Project: limits results to one or more projects.
Issue type: finds bugs, stories, tasks, epics, or custom types.
Status: shows work such as To Do, In Progress, or Done.
Assignee: identifies work assigned to a person.
Reporter: finds issues submitted by a particular person.
Priority: highlights urgent or high-impact work.
Sprint: displays work connected to a selected sprint.
Labels: groups issues with a shared label.

For example, a support lead could select the “Customer Portal” project, choose “Bug,” and set the status to “Open.” The result becomes a practical triage queue.

Step 4: Switch to JQL When You Need More Control

To create a more precise search, select Advanced or JQL. Then enter a query such as:

project = APP AND issuetype = Bug AND statusCategory != Done ORDER BY priority DESC, updated DESC

This query finds unfinished bugs in the APP project, placing higher-priority and recently updated issues first.

Here’s why: JQL lets you combine conditions with AND, broaden results with OR, exclude results with !=, and control ordering with ORDER BY.

Step 5: Test the Results

Run the search and review several results. Check whether every issue belongs in the view and whether important issues are missing.

Try a few edge cases. Look for an unassigned issue, a recently closed issue, or an item without the label you expected.

If the result is too broad, add a condition. If it is too narrow, remove one condition or replace AND with OR where appropriate.

Step 6: Save the Filter

Run the search.
Select Save as.
Enter a clear filter name.
Add an optional description.
Select Save.

Use names that explain purpose and scope. “Open mobile bugs for release 4.2” is clearer than “My filter.”

Step 7: Share the Filter Carefully

Saving a filter makes it available to you. Sharing it allows other people to use it, depending on their project and issue permissions.

Open the saved filter.
Select Details, Edit permissions, or the equivalent option.
Choose a user, group, project role, or approved audience.
Save the permission settings.

Share with the smallest audience that needs access. A team filter may suit a project role, while a leadership view may need a restricted group.

Step 8: Add the Filter to a Dashboard or Board

A saved search becomes more useful when it appears where your team already works.

Add a Filter Results gadget to a dashboard.
Use the filter as a board or backlog view when your Jira setup supports it.
Place it in a subscription for scheduled updates.
Use it in reporting gadgets for trend and workload visibility.

The best part? A single carefully maintained filter can support daily operations, sprint reviews, and management reporting.

JQL Examples for Common Jira Filters

JQL becomes easier when you connect each query to a real team task. The examples below use common field names, but your Jira configuration may include different statuses or custom fields.

Purpose	Example JQL
Open issues in one project	`project = APP AND statusCategory != Done`
High-priority bugs	`issuetype = Bug AND priority in (Highest, High) AND statusCategory != Done`
Issues assigned to you	`assignee = currentUser() AND statusCategory != Done`
Recently updated work	`updated >= -7d ORDER BY updated DESC`
Unassigned issues	`assignee is EMPTY AND statusCategory != Done`
Issues in the current sprint	`sprint in openSprints()`
Overdue work	`duedate < now() AND statusCategory != Done`
Issues with a release target	`fixVersion is not EMPTY ORDER BY fixVersion ASC`

Use AND to Narrow Results

AND requires every condition to match. For example:

project = APP AND assignee = currentUser() AND status = "In Progress"

This shows only your in-progress work in the APP project. Adding conditions can improve relevance, but too many restrictions may hide useful issues.

Use OR to Expand Results

OR returns an issue when at least one condition matches:

priority = Highest OR labels = customer-impacting

Use parentheses when combining several conditions. For example:

project = APP AND (priority = Highest OR labels = customer-impacting)

Without parentheses, Jira may evaluate the query differently than you intended.

Use Relative Dates for Living Views

Relative date functions keep a filter useful over time. A query using -7d continues showing the previous seven days instead of becoming outdated tomorrow.

Examples include created >= -30d, updated >= startOfDay(), and duedate < endOfWeek(). Check Jira’s supported functions before using a complex date expression.

How to Edit, Rename, and Manage Saved Filters

You can change a saved filter whenever the team’s workflow changes. Open the filter, adjust the search, and select Save or Save as, depending on whether you want to replace it or create a new version.

When to Edit an Existing Filter

Edit an existing filter when its purpose remains the same. For example, update a release filter when your team moves from version 4.1 to version 4.2.

Create a separate filter when the purpose changes. A release-readiness view and a developer work queue should not share one confusing query.

Use Clear Names and Descriptions

A good naming pattern includes audience, purpose, and scope:

Engineering | Open Bugs | Mobile App
Support | Customer Escalations | Current Month
Release 4.2 | Unresolved Blockers

Add a description explaining the owner, intended audience, and review cadence. This small detail prevents duplicate filters and abandoned searches.

Check Ownership and Permissions

Filter ownership matters when the creator changes teams or leaves the organization. An administrator may need to transfer ownership or update permissions.

Review shared filters regularly. Remove access that no longer matches the team structure, especially for views containing sensitive project work.

Use Subscriptions Carefully

Jira can send scheduled filter results to selected recipients when subscriptions are available. A daily report can help a support team review unresolved escalations each morning.

Avoid sending broad result sets to large groups. A focused report with clear ownership is more useful than a long notification that people ignore.

Common Filter Mistakes and How to Fix Them

Most filter problems come from scope, field names, permissions, or logic. The query may be valid while the result still fails to answer the intended question.

The Filter Returns Too Many Issues

Add a project, issue type, status category, or date condition. For example, change assignee = currentUser() to:

project = APP AND assignee = currentUser() AND statusCategory != Done

That adjustment removes completed work and issues from unrelated projects.

The Filter Returns No Issues

Remove one condition at a time to find the restriction causing the problem. Check spelling, status names, project keys, and date ranges.

Custom fields can also contain unexpected values. A field may display “Ready for Review” while its internal value differs.

A User Cannot See Expected Results

Filter sharing does not override Jira project permissions. A person may open the saved search but see fewer issues than you do.

Ask an administrator to check project access, issue security, and the person’s group or role membership.

The Query Uses the Wrong Logic

Consider this query:

project = APP AND status = "Open" OR priority = Highest

Depending on evaluation order, the priority condition may include high-priority issues from other projects. Use parentheses:

project = APP AND (status = "Open" OR priority = Highest)

The Filter Becomes Outdated

Fixed sprint names, release labels, and exact dates can age quickly. Replace them with functions such as openSprints() or relative periods where they match your goal.

Still, avoid making every filter dynamic. A historical release report often needs fixed values for accurate comparison.

Jira Filter Best Practices for Teams

A useful filter should answer one recurring question. Before saving it, write that question in plain language.

For example: “Which unresolved, high-priority bugs need attention from the mobile team this week?” Then build conditions that answer only that question.

Start with a narrow purpose.
Use descriptive names and descriptions.
Test results with real edge cases.
Prefer relative dates for ongoing operational views.
Use fixed values for historical reports.
Share only with the necessary audience.
Review ownership after team changes.
Remove duplicate or abandoned filters.
Keep complex JQL readable with spacing and parentheses.
Check permissions before treating missing issues as a query error.

Create a Small Filter Library

Most teams need a few reliable filters rather than dozens of near-duplicates. A practical library might include current sprint work, unresolved bugs, blocked items, unassigned issues, and release risks.

Each filter should have an owner and a review date. That simple responsibility prevents dashboards from displaying stale information.

Separate Personal and Shared Views

A personal filter can reflect your own work style. A shared filter should use team language, stable conditions, and an agreed purpose.

For example, your personal view may show issues updated today. A team view may show all unresolved work grouped by priority.

Jira Filter Solution: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com combines project management and knowledge management in one platform, with AI support through ONES Assistant. ONES Project is the project management product and can serve as a Jira alternative for teams that need structured issue views, workflows, and reporting.

ONES Project and ONES Wiki are sold separately. Teams can choose the project management product, the knowledge management product, or both.

Core Capabilities

Repeated search work slows planning: ONES Project provides customizable views and filters, helping teams return to important work faster.
Complex workflow rules create inconsistent results: Jira-compatible workflows help teams organize statuses and transitions in a familiar way.
Fixed fields cannot reflect every team process: Custom workflows and custom fields let teams capture product, support, engineering, or compliance details.
Sprint tracking becomes scattered across several views: Built-in sprint management connects planned work with active delivery cycles.
Manual updates consume coordination time: Automation can handle recurring actions and reduce repetitive workflow administration.
Reports require extra configuration: Built-in reporting helps teams inspect progress, workload, and delivery patterns.
Plugin-heavy setups increase maintenance: Native capabilities can reduce reliance on multiple extensions for common project workflows.
Cloud-only requirements restrict deployment choices: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
Deployment changes can create feature gaps: The cloud and self-hosted versions provide full feature parity.

Application Scenarios

A software team could create a “release blockers” view showing unresolved high-priority issues, then connect it with sprint planning and reporting. The team sees the same operational picture without rebuilding the query for every meeting.

A regulated organization could use an On-Premise, Private Cloud, or Air-gapped deployment when network restrictions matter. The team can retain structured project workflows while controlling its deployment environment.

A growing product group could use ONES Project for delivery management and add ONES Wiki separately for team knowledge. This arrangement keeps project work and reference material connected without requiring one product purchase for every need.

Common Challenges When Creating Jira Filters

Challenge: The Team Cannot Agree on Filter Purpose

Solution: Write the question first, then define the audience and review frequency. A filter for daily triage needs different conditions from a monthly leadership report.

Challenge: Shared Filters Become Stale

Solution: Assign an owner and review filters during sprint planning or release preparation. Replace old release values and remove views no one uses.

Challenge: JQL Looks Correct but Results Feel Wrong

Solution: Test each clause separately. Then combine the clauses gradually, checking parentheses and operator logic after every change.

Challenge: People See Different Results

Solution: Compare project permissions, issue security, and filter-sharing settings. A shared search does not guarantee identical visibility.

FAQs About Jira Filters

What is the fastest way to create a Jira filter?

Open Jira’s issue search page, select conditions in basic search, run the search, and choose Save as. Give the filter a descriptive name before sharing it. This method works well for project, status, assignee, priority, and issue-type searches. Switch to advanced search when you need functions, custom fields, date logic, or multiple condition groups.

Can I create a Jira filter without knowing JQL?

Yes. Basic search lets you create many useful filters through menus and field selectors. Jira builds the query behind the scenes. You can later switch to advanced search to inspect or refine the JQL. Learning a few operators, such as AND, OR, IN, and ORDER BY, makes more advanced filters easier to maintain.

Why can’t another person see my saved filter?

The filter may still be private, or its sharing permission may target a group or project role that excludes that person. Jira project permissions and issue security can also limit visible results. Check the filter’s sharing settings first, then ask an administrator to review project access and issue-level restrictions.

How do I share a Jira filter with my team?

Open the saved filter and select its details or permission settings. Choose the appropriate group, project role, or approved audience, then save the change. Use the smallest practical audience. A team filter usually belongs with a project role, while a cross-functional report may need a carefully managed group.

What should I do when a Jira filter shows too many issues?

Add conditions that reflect the filter’s purpose. Project, issue type, status category, assignee, priority, label, and date are common choices. Review whether OR is expanding the results unexpectedly. Parentheses can keep multiple conditions together and prevent high-priority issues from unrelated projects appearing in the view.

Can a Jira filter be used on a dashboard?

Yes. A saved filter can power dashboard gadgets such as Filter Results, charts, and other reporting views available in your Jira setup. Choose a concise column set and limit the result scope. A dashboard works best when each gadget answers one question, such as which bugs remain unresolved or which issues are overdue.

Conclusion

Creating a Jira filter means defining a question, choosing conditions, testing the results, saving the search, and sharing it with the right audience. Basic search handles common needs, while JQL gives you precision.

But here's the truth: a filter only stays useful when someone maintains its purpose, permissions, ownership, and time conditions. Review shared views regularly, test unusual cases, and remove abandoned searches.

If Jira filter management becomes difficult across complex workflows, ONES Project offers a Jira alternative with customizable workflows, sprint management, automation, reporting, flexible deployment, and native capabilities. Start with one recurring work question, then build a reliable view around it.