Jira Search, Filters, JQL, Dashboards, Gadgets & Reports

The Use of Filters in Jira

In Jira, a filter is a saved search query that lets users quickly find and access specific issues based on criteria like project, assignee, priority, status, labels, or custom fields.

Filters are often used to organize work, monitor progress, and share views with the team.

How Filters Work

You create a filter using JQL (Jira Query Language) or via the basic search UI.

You can:

• Save a filter with a custom name.

• Share it with your team or keep it private.

• Add it to dashboards.

• Use it in boards.

• Have it emailed on a schedule.

Interview Answer

"Filters in Jira help me quickly find and manage relevant issues. I often create filters to track my open bugs, sprint-specific tasks, or high-priority items. These filters can be reused, shared with team members, and even linked to dashboards for visual tracking. I also use JQL to create more advanced filters based on complex conditions."

What is JQL (Jira Query Language)?

JQL stands for Jira Query Language—a powerful query language used in Jira to search for issues using specific criteria.

It allows users to create customized, precise filters by combining fields, operators, and functions.

Why JQL Is Important

It helps:

• Search issues with precision (beyond what basic search offers).

• Create filters.

• Create custom reports.

• Configure boards.

It is essential for advanced Jira usage in projects, QA, and sprint planning.

Common Fields in JQL

• project

• assignee

• status

• type

• priority

• labels

• created

• updated

• due

• resolution

• reporter

Interview Answer

"JQL is Jira's query language that allows me to search for issues using precise conditions. I use it daily to create filters and track issues—for example, bugs assigned to me or issues created in the last 7 days. JQL is essential in configuring dashboards, Kanban boards, and automating reporting in Jira."

Different Ways to Search for Issues

Basic Search

A user-friendly interface with dropdowns and fields to filter by:

• Project

• Issue Type

• Status

• Assignee

• Priority

• Dates

Suitable for quick filtering without any syntax knowledge.

Advanced Search (JQL)

An SQL-like language for complex queries with multiple conditions and logic.

Example:

project = "MyProject"
AND status = "Open"
AND assignee = currentUser()
ORDER BY priority DESC

Supports operators such as:

• AND

• OR

• NOT

• Wildcards

Filters

Saved searches that can be:

• Shared

• Private

Optional email subscriptions are also available.

Quick Search / Search Bar

The top search bar for quick lookups by:

• Keyword

• Issue Key (e.g., PROJ-123)

• User

Boards and Reports

Agile boards (Scrum/Kanban) provide filtered views by:

• Status

• Sprint

Reports such as:

• Burndown

• Velocity

focus on specific sets of issues.

Jira REST API

For automation or integrations, programmatically search issues using JQL.

Search Issues Created By You / Assigned to a Team Member

Issues Created By You

Basic Search

Set:

• Creator/Reporter = Your Name

(Usually auto-selected as Current User.)

JQL

reporter = currentUser()

Example:

project = "MyProject"
AND reporter = currentUser()
AND created >= -30d

Shows issues created in the last 30 days for a specific project.

Issues Assigned to You or a Team Member

Basic Search

Select:

• Assignee = Current User

• Or choose a specific team member

JQL

For yourself:

assignee = currentUser()

For another user:

assignee = "john.doe"

Additional filters:

By Project

project = "TestAutomation"
AND assignee = currentUser()

By Status

assignee = currentUser()
AND status != Done

Unassigned Issues

assignee IS EMPTY

Interview Answer

"To track tasks assigned to my team or me, I use Jira's 'Search for Issues' feature. I either use the basic filter or write JQL like assignee = currentUser() for myself, or assignee = "TeamMember" to find issues assigned to others. I usually save these as filters and even add them to my dashboard for easy tracking."

Using JQL to Find High-Priority Bugs from the Last 7 Days

JQL Query

issuetype = Bug
AND priority = High
AND created >= -7d
ORDER BY created DESC

Explanation

• issuetype = Bug → filters only bugs.

• priority = High → filters high-priority bugs.

• created >= -7d → filters issues created within the last seven days.

• ORDER BY created DESC → newest issues appear first.

Interview Answer

"I use JQL to filter bugs with high priority created in the last 7 days by combining conditions on issue type, priority, and creation date. The relative date '-7d' helps me get recent issues dynamically without changing the query."

How to Create a Custom Filter

A custom filter saves specific issue search criteria (via JQL or basic search) as a reusable, shareable filter.

Option 1 – Basic Search

Go to:

Issues → Search for Issues

Set the filter criteria.

Example:

• Project = QA

• Status = To Do

• Assignee = You

Click:

Save As

Name the filter.

Example:

My To Do Tasks

The filter becomes available under:

Filters → View All Filters

Option 2 – JQL

Go to:

Issues → Search for Issues → Switch to JQL

Type your query.

Example:

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

Click:

• Search

• Save As

Example filter name:

My In-Progress CRM Issues

Bonus Features

You can:

• Subscribe to the filter for daily or weekly emails.

• Share it with your team or groups.

• Use it on dashboards as gadgets such as:

  • Filter Results

  • Pie Chart

Real-life Example

To track all open bugs assigned to you:

project = "EcommerceApp"
AND type = Bug
AND status != Done
AND assignee = currentUser()

Save As:

My Open Bugs

Each morning, simply open the saved filter to view pending bugs.

Interview Answer

"To manage my tasks efficiently, I often create custom filters in Jira. I either use the basic search or write a JQL query to define my criteria, like open bugs assigned to me. After searching, I save the filter and use it daily or even share it with the team. This helps in organizing sprint work, reviews, and bug triage meetings."

How to Create a Dashboard

A dashboard is a customizable page where users visualize key project information—bugs, tasks, sprint progress, and team performance—using gadgets.

It serves as a control panel for monitoring project health.

Step-by-Step

Navigate to:

Dashboards → View All Dashboards → Create New Dashboard

Fill in:

• Name

• Description (optional)

• Share Settings

  • Private

  • Project Team

  • Specific Users/Groups

Click:

Create

Then:

• Click Add a Gadget.

• Choose a gadget.

• Configure it.

• Save.

Finally:

• Drag and drop gadgets.

• Rearrange and resize them.

Real-life Example

As a QA Lead tracking:

• Total bugs

• Bugs per team member

• Bugs by status

Create these filters:

project = "WebApp"
AND type = Bug

project = "WebApp"
AND type = Bug
ORDER BY assignee

project = "WebApp"
AND type = Bug
AND status != Done

Add gadgets:

• Filter Results

• Pie Chart

• Two-Dimensional Filter

Interview Answer

"I use Jira dashboards to monitor the health of our QA activities. I create dashboards using saved filters and gadgets such as Filter Results, Pie Chart, and Created vs. Resolved. For example, I track open bugs by severity or assignee. It helps me stay on top of critical defects and share progress with stakeholders in stand-ups and sprint reviews."

Gadgets Used on Jira Dashboards

Gadgets are widgets that display key information on dashboards.

Commonly used gadgets include:

Interview Answer

"On my project, I created a QA dashboard using Jira gadgets to track our testing KPIs. I used gadgets like Filter Results to list open bugs, the Pie Chart to show bug distribution by severity, and the Two-Dimensional Filter to show bug status by assignee. These helped in our daily stand-ups and sprint reviews to keep the team aligned and proactive about quality."

Jira Reports (Burndown, Velocity & More)

Burndown Chart

Shows how much work remains in a sprint over time.

Ideal for Scrum teams to track sprint pace.

Velocity Chart

Shows work completed per sprint.

Helps estimate team capacity and plan future sprints.

Sprint Report

Summarizes:

• Completed issues

• Incomplete issues

• Added issues

Useful for retrospectives.

Cumulative Flow Diagram

Visualizes issue status across workflow stages.

Helps identify bottlenecks.

Control Chart

Shows cycle or lead time for issues.

Helps analyze delays.

Issue Statistics Report

Counts issues grouped by:

• Priority

• Assignee

• Status

Useful for workload analysis.

Version Report

Tracks progress toward completion of a specific release.

Interview Answer

"I use Jira reports like the Burndown Chart to track sprint pace, the Velocity Chart to plan capacity, and the Sprint Report for retrospectives. For deeper analysis, I use the Cumulative Flow Diagram to spot bottlenecks and the Control Chart to measure cycle time."

Exporting Jira Data

Jira data can be exported using:

• Jira's built-in export feature (such as CSV or Excel).

• Jira plugins for advanced reporting.

• The REST API for automated exports.

FAQs

1. What is a filter in Jira?

A saved search query (built via JQL or basic search) used to find and organize issues by criteria like project, assignee, priority, or status, and shareable with the team.

2. What is JQL?

Jira Query Language—a query language for precise issue searches by combining fields, operators, and functions. It powers filters, dashboards, boards, and reports.

3. How do you find issues created by or assigned to you?

Use basic search on Reporter or Assignee, or JQL:

• reporter = currentUser() for issues you created.

• assignee = currentUser() for issues assigned to you.

4. What JQL finds high-priority bugs from the last 7 days?

issuetype = Bug
AND priority = High
AND created >= -7d
ORDER BY created DESC

5. How do you create a custom filter?

Search with basic filters or JQL, click Save As, name the filter, and save. You can then subscribe to it, share it, or add it to a dashboard.

6. How do you create a dashboard in Jira?

Go to Dashboards → Create New Dashboard, set the name and share settings, add and configure gadgets using saved filters, then arrange them.

7. What reports have you used in Jira?

• Burndown

• Velocity

• Sprint Report

• Cumulative Flow Diagram

• Control Chart

• Issue Statistics

• Version Report