Improve your bottom line with accurate time/cost reporting

Jira search: How to find issues quickly using JQL

Improve Jira search efficiency and accuracy by using JQL to create custom queries. Then, save and distribute them for repeated use.

Jira search: How to find issues quickly using JQL

Nobody has hours to spend sifting through issues in a Jira dashboard to find important information. Instead, conduct a quick and accurate Jira search using Atlassian’s native query language, JQL. 

Here, we’ll explain what JQL is and show you how to use Jira’s JQL to find the data you need in a fraction of the time.

Getting started with search in Jira

Learning a programming language might be intimidating if you’re not technologically inclined. Don’t worry; Atlassian Jira comes equipped with two flexible search options. We’ll start with the basic search function.

The basic search method is user-friendly, leveraging the search bar at the top right of the .  Use this version of the search function to look for the following:

  • A specific issue: Locate issues according to their label, like JobKey-11

  • Text: Find information based on keywords in the issue’s summary, description, and comments.

  • Smart Query: Typing “my open bugs” will return a list of bugs assigned to the user. 

Other include using the search bar’s drop-down menu to locate data based on specific Jira fields, such as:

  • Issues

  • Boards

  • Projects

  • Filters 

  • Plans

  • Assignees

These methodologies comprise Jira’s basic search function.

Advanced searches in Jira

Jira’s basic search function is limited and offers only a high-level view of data. The advanced search function is a better solution when you require refined search results.

Advanced searching leverages Atlassian’s Jira Query Language (JQL). JQL is an intuitive tool that allows users to create search queries that deliver precise results using criteria unavailable to basic searches.

How to create a JQL query

Follow these steps to access the advanced search function:

  1. Open the Jira project related to the search

  2. Select “Issues” from the navigation sidebar

  3. Click “Advanced Issue Search”

  4. In the search window, click “JQL” to switch to Jira Query Language mode

  5. Define the search criteria

  6. Click the “Search” button to the right of the search window

How to save and share a JQL filter

Atlassian’s JQL lets users convert search queries into filters for repeated use. Team members can share these JQL filters, streamlining search functions for everyone.

Once a user runs a , they can save it by following these steps:

  1. Click the “Save as” filter to open the Save Filter window

  2. Name the filter

  3. Enable the “Sync Filter” toggle to make it accessible from the dashboard and Jira Software Boards

  4. Define who can access the filter

  5. Click “Save”

Essential JQL syntax

Putting together a query using the appropriate Jira search syntax takes some practice. Queries use a string of elements to define the desired information. Each query has at least three components – a field, an operator, and some number of values or functions. These pieces may be modified by keywords.

Here’s a summary of how these components fit into Jira Query Language, plus examples of their use.

Field

Jira fields define where the system should search. Some standard fields include:

  • Priority: This field locates issues with a specific priority.

priority = High

priority = 10000

  • Description: This field will identify issues with descriptions that contain a particular word or text string.

description ~ “Please see screenshot”

  • IssueType: Using this field in a JQL query will return a specific issue category.

issueType = Bug

issueType = Improvement

  • Labels: Labels are a personalized field in Jira that allows users to create custom issue categories.

labels = “labelName”

  • DueDate: You can also locate issues according to a defined due date.

due = “2011/01/15”

  • FixVersion: Search by version name or ID to find issues assigned to a particular fix version.

fixVersion in (“3.14”, “4.2”) 

Operator

The operator defines how the field relates to the value. Here are some common operators:

  • Equals (=): The query delivers results that match the specified value.

assignee = “Nancy Lewis”

  • Not equals (!=): Returns issues where the specified field does not match the requested value. Note that the != operator does not return results where the field has no value.

assignee != “Nancy Lewis”

  • Greater than (>) or less than (<): These operators search for issues where the value is greater than or less than a specified value.

votes > 10

priority < High

  • Greater than equals (>=) or less than equals (<=): Adding the equals sign (=) to greater than (>) or less than (<) operators will also return results that match the value.

votes >= 10

priority <= Normal

  • Contains (~): This operator searches for issues where the field value matches the specified value. It only works on text fields, such as Summary or Description.

summary ~ “word string” 

description ~ “specific phrase”

Value 

Values go after the operator and define the data the user wishes to retrieve. For example, if you’re searching for high-priority issues, you might use the following advanced search prompt:

priority = High

Here, “High” is the value you wish to retrieve.

Keywords

Keywords are specific words within the JQL language that alter the logic or results of a query to further expand and refine it. Here are some examples:

  • AND: Tells JQL to retrieve information that fulfills both clauses.

project = LearnJQL AND status = “In Progress”

  • Or: Returns issues that fulfill either criteria.

project = LearnJQL OR status = “In Progress”

  • Not: Negates an individual clause or complex JQL query, returning only results that don’t fulfill the search criteria.

not assignee = jsmith

not (reporter = jsmith or reporter = lewis)

Functions

are words followed by parentheses, which may or may not contain values or fields. Functions perform a calculation on specific Jira data or the content of the parentheses.

For example, if you wanted to find issues assigned to you that are due before the end of the day, you could enter the following advanced search query:

assignee = currentUser() AND due < endOfDay()

To find assignments due before the end of tomorrow, simply add a value into the parentheses – like so:

assignee = currentUser() AND due < endOfDay(“+1”)

Jira search examples

Here are a few JQL examples to show you how these components come together to form advanced search queries:

  • Imagine you want to retrieve information regarding project bugs reported by a specific team member. You might enter a query with the following syntax:

reporter = nlewis AND project = LearnJQL

The keyword “AND” ensures this search returns all bugs Nancy Lewis reported within the project LearnJQL.

  • Now, say you want to discover issues within a specific project that are marked with one of several priorities.

priority in (Blocker, Critical) AND project in (LearnJQL, JQLlessons, StudyJQL)

The operator “in” returns any items that match the values between the parenthesis – in this case, issues with “critical” or “blocker” priority levels located within any of the three listed projects.

  • Finally, here’s a query to identify unassigned issues created in the last 24 hours.

assignee is empty AND created >= “-1d”

Including “is empty” in the JQL query returns issues with a blank assignee field. The search also introduces how Jira supports relative dates, with “-1” evaluating one day behind the date that the query runs. 

Enhancing Jira search and reporting with Tempo

Tempo’s tools integrate with Atlassian Jira to expand JQL’s accessible data pool and increase the power of your .

For example, Tempo’s offers custom dashboards and automated reporting to provide detailed analytics derived from refined Jira search results. Adding Timesheets to your tech stack enhances reporting capabilities by introducing advanced time and resource-tracking data to your information pool.  

Timesheets overview

#1 Jira time tracking app

Other Popular Features

related-content-image

    related-content-image

      related-content-image

        related-content-image

          related-content-image

            related-content-image

              related-content-image

                related-content-image

                  related-content-image

                    Streamline your workflow, in-and-out of Jira

                    Tempo's products help teams increase productivity and communicate across their organization.

                    Tempo’s intuitive automation and Jira-native design make it the most trusted time tracking tool for enterprise organization.

                    A powerful team resource management tool designed to optimize capacity planning and project management in Jira

                    Visualize all your Jira data & manage portfolios of projects in real-time.

                    The roadmapping tool designed for high-performing teams delivering boardroom-ready strategic roadmaps.

                    Frequently Asked Questions

                    Couldn't find what you need?Go to our

                    JQL syntax is similar to SQL, but the resemblance ends there. Developers use SQL, which stands for Structured Query Language, to store and process information within a relational database.

                    JQL was created by Atlassian for technical and nontechnical users to find, analyze, and report on data within the Jira project management application.

                    Several third-party plugins and boosters in the can expand JQL’s search capabilities.

                    Start optimizing your time

                    Access a free trial of Timesheets.