How to Create a Jira Filter: 7 Steps and Clear Examples

Struggling to find the right Jira issues? Learn how to create a Jira filter in 7 steps using basic search or JQL, then save and share your view. Read now.

To create a Jira filter, search for the work items you need, refine the criteria, and save the search for reuse. You can build a filter with Jira’s basic search controls or write a JQL query for more precision.

That sounds simple until a team needs one view for overdue bugs, another for a sprint, and a third that colleagues can access. A vague query can hide important work, while a private filter may leave teammates staring at an empty results page.

But here's the truth: a useful filter starts with a clear question and a small set of conditions. I’ll walk you through seven practical steps, share JQL examples, and explain how to share and maintain your filters. You’ll finish with a repeatable method for turning a Jira search into a reliable team view.

How to create a Jira filter in 7 steps

Follow these steps to build, save, and share a filter. Jira’s menus can vary by version and configuration, so look for the issue-search or work-item-search page if a label differs.

Open issue search. In Jira, open the Filters menu and choose the search option, or navigate to the issue search page through your Jira project menu. You should see controls for searching and displaying work items.
Choose Basic or JQL search. Basic search is a good starting point when you want to filter by common fields such as project, status, assignee, or issue type. Switch to JQL when you need more control over conditions and sorting.
Set the scope. Start with a project or another clear boundary. For example, select the mobile app project before adding conditions for open bugs. This keeps unrelated work out of the results.
Add criteria that answer one question. Add conditions such as status, priority, assignee, or label. In JQL, a query for unresolved bugs in a project might look like project = APP AND issuetype = Bug AND resolution = Unresolved.
Check the results. Review several returned issues and confirm they match your goal. If you wanted active sprint work, check that completed work and issues from other projects aren’t included.
Save the search. Choose the option to save the current search as a filter, then give it a descriptive name such as APP – Unresolved Bugs. A useful name tells teammates what the results contain.
Set access and optional updates. Open the saved filter’s details to manage sharing, where available. Choose an appropriate project, group, or user audience, then consider a subscription if people need regular email updates.

The best part? Once saved, you can return to the filter, edit its criteria, and adjust its sharing settings as the team’s needs change.

Jira product screenshot

What a Jira filter does—and when to use one

A Jira filter is a saved search that returns work items matching criteria you define. It can help you focus on a project, status, person, date, label, or combination of fields without rebuilding the search each time.

For example, a support lead might save a view of high-priority tickets awaiting review. A developer could keep a separate filter for bugs assigned to them during the current sprint.

Here's why: filters can also power dashboards and scheduled email subscriptions, depending on your Jira setup and permissions. A well-named filter becomes a reusable view for a routine task, such as a Monday backlog review.

JQL examples for common Jira filters

JQL lets you express conditions with fields, operators, and values. Begin with a query you can explain in one sentence, then add complexity only when the results require it.

Open issues in one project: project = APP AND statusCategory != Done
Issues assigned to you: assignee = currentUser() AND resolution = Unresolved
High-priority bugs: issuetype = Bug AND priority in (Highest, High) AND resolution = Unresolved
Issues updated in the past week: project = APP AND updated >= -7d
Work in the current sprint: project = APP AND sprint in openSprints()

Field names and available functions may differ with Jira configuration. If a query returns an error, check the field spelling and whether the project uses that field.

Let me explain: combine conditions carefully. AND narrows results because every condition must match; OR broadens them because either condition can match. Parentheses can make mixed logic easier to read, as in project = APP AND (priority = High OR labels = customer-impact).

Sharing filters and managing access

Saving a filter makes it available to you, but colleagues may need explicit permission to view or edit it. Check the filter’s details or permissions area and choose an audience that matches its purpose.

For a personal work queue, private access may be enough. For a team dashboard, sharing with the relevant project role or group can prevent each person from recreating the same search.

You might be wondering: why can a teammate still see no results? They may lack permission to view the underlying project issues, even if they can open the filter. Filter access and issue access are separate considerations.

Subscriptions can send regular updates to selected recipients, where enabled. Before setting one up, confirm that the audience needs the email and that the filter’s results are appropriate for everyone receiving it.

Keep saved filters accurate and useful

A filter can become less useful when its project, workflow, or team habits change. Review important searches when statuses are renamed, custom fields are updated, or a team changes how it labels work.

Use names that communicate both subject and purpose. APP – Bugs for Triage is easier to recognize than My Search 2, especially when a team has many saved views.

For a recurring report, test the filter with realistic examples before connecting it to a dashboard or subscription. If a weekly review unexpectedly includes completed work, adjust the status condition and verify the returned issues again.

Troubleshooting Jira filter problems

The filter returns no issues. Remove one condition at a time and test again. A project key, status, assignee, or label may be too restrictive or misspelled.
The results include unwanted work. Check each condition and how AND and OR interact. Add parentheses when a query mixes both operators.
A teammate cannot open the filter. Review the filter’s sharing permissions. Then confirm that the teammate can access the relevant project and issues.
The filter is missing from a dashboard. Check that the dashboard gadget uses the intended saved filter and that the viewer has the required permissions.

Here's a practical test: compare the results with two or three issues you already know should match. That small check can reveal a logic mistake before it affects a team review.

Project and knowledge management with ONES.com

Value proposition: ONES.com brings project management and knowledge management together through ONES Project and ONES Wiki, sold separately. For teams assessing a Jira alternative, ONES Project combines Jira-compatible workflows with project features and deployment choices.

ONES.com product screenshot

Creating filters is only one part of project visibility. A team may also need consistent workflows, useful reporting, and an environment that fits its security requirements.

Core capabilities

When Jira workflows feel difficult to adapt: ONES Project supports Jira-compatible workflows and custom workflows, helping teams shape work stages around their process.
When teams need project-specific information: Custom fields let teams capture details that standard issue fields may not cover, making work items more relevant to each project.
When sprint planning and delivery need structure: Sprint management supports teams that organize work into iterations and need to track progress through them.
When repeated tasks consume time: Automation can handle suitable routine actions, reducing manual steps for recurring project workflows.
When progress is hard to assess: Built-in reporting gives teams project visibility without relying on a collection of separate reporting plugins.
When plugin maintenance adds overhead: Native project capabilities can reduce dependence on plugins for supported needs, helping teams manage a more integrated environment.
When hosting requirements are specific: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, giving organizations options for their operating environment.
When teams need self-hosting and feature consistency: Cloud and self-hosted versions have full feature parity, so deployment choice does not require giving up feature availability.

Application scenarios

A product team moving from Jira might use ONES Project to manage sprint work, tailor issue fields, and review progress through built-in reporting. The team can evaluate whether its familiar workflow needs can be handled with fewer separate plugins.

An organization with restricted-network requirements could assess an Air-gapped or On-Premise deployment. A smaller team can also explore the free plan, which supports up to 30 seats, before deciding whether the platform suits its needs.

For teams that also want a knowledge base, ONES Wiki is a separate Confluence alternative within the ONES.com offering. That lets a team consider project and knowledge management together while selecting the products that fit its requirements.

Common challenges when creating Jira filters

Too many conditions make the search hard to understand. Start with the essential project and status criteria. Add one condition at a time, checking that each one improves the results.
Filter names become unclear over time. Use a consistent naming pattern that identifies the project and purpose. Rename outdated filters so people can distinguish active views from old experiments.
Sharing creates access confusion. Explain who the filter is for, then check both filter permissions and project access. A shared search cannot grant access to issues by itself.
Subscriptions create unnecessary messages. Choose a useful frequency and audience. Review the recipients periodically, especially when team responsibilities change.

FAQs about Jira filters

Can I create a Jira filter without knowing JQL?

Yes. Basic search lets you select common criteria, such as project, status, assignee, and issue type, through controls in the search page. Save the search when its results match your goal. JQL is helpful when you need more precise conditions, date logic, or combinations that basic search does not offer. You can start with Basic search and switch to JQL as your needs grow.

How do I share a Jira filter with my team?

Open the saved filter’s details or permissions area and select an available sharing option, such as a project role, group, or specific people. The exact choices depend on your Jira configuration and permissions. Also confirm that recipients can access the issues themselves. Sharing the filter gives access to the saved search, while project permissions govern access to its results.

Why does my Jira filter show no results?

One of the conditions may be too restrictive, or a field value may not match your Jira setup. Remove conditions one by one, check project keys and field names, and test the search again. For JQL, review the operators and parentheses. It can also help to compare the returned issues with a known example that should match the filter.

Can I use a Jira filter on a dashboard?

Yes, many Jira dashboards include gadgets that display results from a saved filter. Add or configure a suitable gadget, then select the filter you want it to use. The dashboard viewer may also need permission to view the filter and the underlying issues. If the gadget appears empty to a teammate, check both kinds of access before changing the query.

What is the difference between saving and sharing a Jira filter?

Saving keeps a search so you can return to it later. Sharing controls which people or groups can access that saved search, where the relevant permissions are available. These are separate actions: a saved filter may remain private until you change its access settings. Recipients still need permission to view the matching project issues.

Conclusion

A reliable Jira filter begins with a clear question, a focused set of criteria, and a careful review of the results. Save it with a descriptive name, then check access before using it for a team dashboard or subscription.

When a search feels complicated, remove conditions and rebuild it one step at a time. That approach helps you catch query errors and keep the final view useful as your team’s work changes.

If your team is also reviewing project workflows, reporting, or deployment needs, ONES Project is a Jira alternative worth assessing alongside your filter process. Choose the approach that gives you clear, maintainable views of the work that matters.