How To Create A Filter In Jira: Step-By-Step Guide With Examples

Jira filters are like magic glasses. They help you see exactly what you need. No clutter. No confusion. Just the issues that matter. If you’ve ever felt lost in a sea of tickets, this guide is for you.

TLDR: Creating a filter in Jira helps you quickly find and organize issues. You use JQL (Jira Query Language) or basic search fields to define what you want to see. Once created, filters can be saved, shared, favorited, and even used in dashboards. It’s simple, powerful, and a total time saver.

Let’s break it down step by step. And yes, we’ll keep it fun and easy.


What Is a Filter in Jira?

A filter in Jira is a saved search. That’s it.

You tell Jira what issues you want to see. Jira remembers your request. Next time, you click once. Boom. Results appear.

Filters help you:

  • Track your tasks
  • Monitor sprint progress
  • Find overdue issues
  • Watch high-priority bugs
  • Create dashboard reports

Simple idea. Big impact.


Step 1: Go to the Issue Search Page

First, log into Jira.

At the top menu, click on Filters. Then click View all issues.

This opens the issue search screen.

Image not found in postmeta

Here’s what you’ll see:

  • A search bar at the top
  • Filter options like project, type, status
  • A list of issues below

You’re ready to build your filter.


Step 2: Choose Basic Search or JQL

Jira gives you two ways to create filters:

  • Basic mode (point and click)
  • JQL mode (advanced search using code-like queries)

If you’re new, start with Basic.

If you want power and precision, use JQL.

Using Basic Search

In Basic mode, you’ll see dropdowns like:

  • Project
  • Issue Type
  • Status
  • Assignee
  • Priority

Example:

  • Project = Website Redesign
  • Status = In Progress
  • Assignee = Me

That’s your filter.

Jira instantly shows matching issues.

Using JQL (Jira Query Language)

JQL looks technical. But it’s not scary.

Here’s the same example in JQL:

project = “Website Redesign” AND status = “In Progress” AND assignee = currentUser()

See? Just structured sentences.

Other helpful JQL examples:

  • priority = High
  • duedate <= now()
  • status = Done AND updated > -7d

JQL gives you total control.


Step 3: Refine Your Results

Now tweak your search.

Ask yourself:

  • Do I need a specific label?
  • Should I filter by sprint?
  • Only unresolved issues?

Add conditions one at a time.

Watch the results change live.

This is the fun part. You’re shaping your view.

Image not found in postmeta

Step 4: Save the Filter

Once you’re happy, save it.

Click Save As at the top right.

Give your filter a clear name.

Good examples:

  • My Open Bugs
  • Sprint 12 Completed Tasks
  • High Priority This Week

Bad example:

  • Filter123

Be descriptive. Your future self will thank you.

After naming it, click Submit.

Done. Your filter is saved.


Step 5: Share the Filter (Optional)

Sometimes filters are just for you.

Sometimes your whole team needs them.

To share:

  • Go to Filters
  • Select Manage Filters
  • Click the three dots next to your filter
  • Choose Edit

Under permissions, add:

  • Project
  • Group
  • Specific users

Now others can use it too.

Team productivity just leveled up.


Step 6: Add Filter to a Dashboard

Here’s where filters become powerful.

Filters fuel dashboards.

To add one:

  • Go to Dashboards
  • Click Create dashboard (or edit existing)
  • Click Add gadget

Common gadgets:

  • Filter Results
  • Pie Chart
  • Created vs Resolved Chart
  • Two Dimensional Statistics

Select your saved filter inside the gadget settings.

Instant reports. Zero spreadsheets.

Image not found in postmeta

Real-Life Examples of Useful Filters

Let’s look at practical filters you can copy today.

1. My Overdue Tasks

assignee = currentUser() AND duedate < now() AND status != Done

Perfect for daily checks.

2. Unassigned High-Priority Bugs

issuetype = Bug AND priority = Highest AND assignee is EMPTY

Great for team leads.

3. This Week’s Completed Tasks

status = Done AND updated >= -7d

Ideal for sprint reviews.

4. Issues in Current Sprint

sprint in openSprints()

Quick sprint visibility.


Basic Search vs JQL: Comparison

Feature Basic Search JQL
Ease of Use Very easy Medium
Customization Limited Very powerful
Best For Beginners Advanced users
Speed Fast setup Fast once learned
Complex Queries Not supported Fully supported

Tip: Start basic. Move to JQL when you’re ready.


Common Mistakes to Avoid

Let’s save you some headaches.

1. Forgetting to Save

You close the page. Your filter disappears.

Always click Save As.

2. Naming Filters Poorly

“Test” is not helpful.

Be clear and specific.

3. Not Checking Permissions

Your team says they can’t see it.

Check sharing settings.

4. Overcomplicating JQL

Keep queries clean.

If it feels confusing, simplify.


Pro Tips for Power Users

Ready to level up?

  • Use ORDER BY to sort results.
    ORDER BY priority DESC
  • Use relative dates like:
    -1d (yesterday)
    -7d (last week)
  • Combine conditions smartly:
    AND narrows results
    OR expands results

Example:

(priority = High OR priority = Highest) AND status != Done

That’s precision filtering.


Why Filters Matter More Than You Think

Without filters, Jira feels noisy.

Too many tickets. Too many updates.

With filters, you control the noise.

You focus only on:

  • Your work
  • Your deadline
  • Your sprint

Managers track progress.

Developers track tasks.

QA tracks bugs.

Everyone wins.


Quick Recap

Here’s the entire process in simple steps:

  1. Go to Filters → View all issues
  2. Choose Basic or JQL
  3. Define your search criteria
  4. Click Save As
  5. Name your filter
  6. Share or add to dashboard if needed

That’s it.

No complicated setup. No technical headaches.


Final Thoughts

Creating filters in Jira is not just a technical skill.

It’s a productivity superpower.

Start small. Create one filter today.

Maybe “My Open Tasks.”

Use it every morning.

Then build more.

Soon, you won’t imagine using Jira without filters.

Clear views. Faster work. Less stress.

And honestly? That’s what good tools are supposed to do.