#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Search & Filters

JQL Queries and Filters

JQL, or Jira Query Language, lets you search for issues using precise, structured criteria instead of relying only on Jira's basic search. Once you're comfortable with JQL, you can build filters that answer exact questions about your project's work.

Writing Basic JQL Queries

A JQL query is built from fields, operators, and values, such as project = "Website Redesign" AND status = "In Progress". You can combine multiple conditions using AND, OR, and NOT to narrow results down to exactly the issues you need to see.

Saving Filters for Reuse

Once a JQL query returns the results you want, you can save it as a filter and reuse it on dashboards, boards, or shared with your team. Saved filters are especially useful for recurring reports, like all bugs opened this month or all overdue tasks assigned to a specific person.

Common JQL Building Blocks

  • project — filter issues within a specific project
  • status — filter by current workflow status
  • assignee — filter by who the issue is assigned to
  • created / updated — filter by date ranges
  • ORDER BY — sort results by priority, date, or other fields

Operators Worth Learning First

Fields and values only get you halfway. The operator decides how strictly Jira matches them, and choosing the right one removes most of the frustration people feel with JQL.

OperatorMeaningExample
= and !=Exact match or exclusionpriority = High
IN / NOT INMatch any value in a liststatus IN ("To Do", "In Progress")
~Text contains (word search)summary ~ "login"
IS EMPTY / IS NOT EMPTYField has no valueassignee IS EMPTY
>, <, >=, <=Compare dates or numberscreated >= -7d
WAS / CHANGEDLook at history, not just current valuestatus WAS "Blocked"

Functions make queries reusable. currentUser() means whoever is running the filter, openSprints() picks active sprints, and startOfWeek() or endOfDay() give moving date boundaries so the filter never needs editing.

Queries You Can Paste and Adapt

-- My unresolved work, most urgent first
assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC, updated DESC

-- Bugs in the active sprint of one project
project = SHOP AND issuetype = Bug AND sprint IN openSprints()

-- Overdue items that are not finished
duedate < now() AND statusCategory != Done

-- Unassigned high-priority tickets created in the last 3 days
assignee IS EMPTY AND priority IN (Highest, High) AND created >= -3d

-- Work moved to Done this week
status CHANGED TO "Done" DURING (startOfWeek(), now())

Replace the project key and field values with your own. Using statusCategory instead of a list of status names keeps a filter working even when a team renames its workflow statuses.

Turning Filters Into Team Tools

A saved filter becomes far more useful once others can rely on it. A practical workflow looks like this:

  1. Write and test the query in advanced search until the result list is right.
  2. Save it with a clear name such as "SHOP - open bugs in sprint".
  3. Edit the filter's sharing settings so the right group or project can view it.
  4. Add it to a dashboard gadget, such as a filter results list or a pie chart grouped by assignee.
  5. Create a subscription so the results arrive by email on a schedule, which suits weekly status reports.

Boards also run on filters. Changing a board's filter changes which issues appear on it, so edit board filters carefully and tell the team when you do.

Where JQL Usually Goes Wrong

  • Missing parentheses. project = A AND status = Open OR status = Reopened returns reopened issues from every project. Wrap the OR part in brackets.
  • Unquoted values with spaces. Status names like In Progress must be in double quotes.
  • Expecting ~ to be exact. Text search matches words and stems, so it may return more than you expect. Use = for exact field values.
  • Hardcoding people's names. A filter built with a specific user breaks when that person moves teams. Prefer currentUser() or a group with membersOf().
  • Sharing a filter nobody can see. If viewers lack permission for a project, those issues silently disappear from their results.

Good habit: keep a short personal list of tested queries. Most daily questions about your project can be answered by tweaking one of them.

Master Jira with Expert-Led Training

Hands-on classes, mentor support, and placement assistance — all in one course.

Explore Jira Course