Table of Contents

    Filters and JQL

    Rumman Ansari June 03, 2026 16 views Subject Details

    Jira for Scrum Masters: Filters and JQL

    Filters and JQL (Jira Query Language) are powerful Jira features that help Scrum Masters and Agile teams quickly search, organize, analyze, and monitor issues across projects and Sprints.

    Key Idea:
    JQL is to Jira what SQL is to databases—it allows users to find exactly the issues they need using custom queries.

    What are Jira Filters?

    A Filter is a saved search that displays issues matching specific criteria. Filters can be reused in dashboards, boards, reports, and subscriptions.

    Example:
    Show all open bugs assigned to the QA team.

    What is JQL?

    Jira Query Language (JQL) is Jira's advanced search language used to search issues based on fields, values, operators, and conditions.

    Basic JQL Syntax:

    Field → Operator → Value

    Why Scrum Masters Use Filters and JQL

    Purpose Benefit
    Sprint Monitoring Track Sprint progress quickly
    Issue Analysis Identify blockers and risks
    Reporting Create custom dashboards and reports
    Team Visibility Focus on relevant work items

    Common JQL Fields

    Field Description
    project Project name or key
    assignee Assigned team member
    status Issue status
    priority Issue priority
    issuetype Story, Task, Bug, Epic, etc.
    sprint Sprint information
    labels Issue tags
    created Creation date

    Common JQL Operators

    Operator Meaning
    = Equals
    != Not Equals
    IN Matches multiple values
    NOT IN Excludes values
    AND Combines conditions
    OR Alternative conditions
    ORDER BY Sorts results

    Basic JQL Examples

    Show all issues in a project:
    project = "ECOM"

    Show all open issues:
    status = "Open"

    Show all bugs:
    issuetype = Bug

    Show issues assigned to a user:
    assignee = currentUser()

    Sprint-Related JQL Examples

    Current Sprint Issues:
    sprint in openSprints()

    Completed Sprint Issues:
    sprint in closedSprints()

    Incomplete Issues in Current Sprint:
    sprint in openSprints() AND status != Done

    Scrum Master JQL Examples

    Use Case JQL Query
    High Priority Issues priority = High
    Blocked Issues status = Blocked
    Unassigned Work assignee IS EMPTY
    Open Bugs issuetype = Bug AND status != Done
    Stories in Current Sprint issuetype = Story AND sprint in openSprints()

    Advanced JQL Examples

    High Priority Open Bugs:
    issuetype = Bug AND priority = High AND status != Done

    Issues Created Last 7 Days:
    created >= -7d

    Issues Assigned to Current User:
    assignee = currentUser()

    Stories Sorted by Priority:
    issuetype = Story ORDER BY priority DESC

    Creating a Saved Filter

    1. Open Jira Search
    2. Select Advanced Search
    3. Enter JQL Query
    4. Run Search
    5. Click Save As
    6. Provide Filter Name
    7. Share with Team if required

    Using Filters in Dashboards

    Saved Filters can be used in Dashboard Gadgets such as:

    • Filter Results Gadget
    • Pie Chart Gadget
    • Created vs Resolved Chart
    • Two-Dimensional Statistics
    • Issue Statistics Gadget

    Role of Scrum Master

    • Create Sprint monitoring filters
    • Track blocked and high-priority issues
    • Support reporting and dashboards
    • Provide visibility to stakeholders
    • Analyze Sprint health using JQL queries

    Best Practices

    • Use meaningful filter names
    • Save frequently used searches
    • Keep JQL queries simple when possible
    • Share useful filters with the team
    • Use filters to drive dashboard reporting

    Common Mistakes

    • Creating overly complex JQL queries
    • Using outdated filters
    • Not documenting important filters
    • Ignoring query performance
    • Creating duplicate filters

    Real-World Example

    Scenario:

    A Scrum Master wants to identify all unfinished work before the Sprint ends.

    JQL:
    sprint in openSprints() AND status != Done

    This instantly displays all incomplete issues that may impact the Sprint Goal.

    Example Interview Answer

    Answer:
    Filters and JQL in Jira are used to search, organize, and analyze issues efficiently. JQL allows advanced querying of project data, while saved filters can be reused in dashboards, reports, and boards. As a Scrum Master, I use JQL to track Sprint progress, identify blockers, and provide visibility to stakeholders.

    Conclusion

    Filters and JQL are among the most powerful features in Jira. They enable Scrum Masters to gain deep insights into project data, monitor Sprint health, create meaningful reports, and improve decision-making throughout the Agile lifecycle.

    Scrum Master Complete Bootcamp: From Beginner to Professional