Introduction to JQL: Standard & advanced search in ..

The next simple search interface is the Search Issues screen. The basic version of this tool allows a user to filter based on any available fields in their instance. It is not limited to the small number of fields used by the Search box. The filtering is performed via an easy to use graphical user interface consisting of drop-downs and input fields. This interface is pre-set with some common fields, such as project, issue type, status, and assignee.

Relative dates (-7d, startOfWeek()) keep your filters dynamic and up-to-date. These are my observations formed from current experience in answering the most frequent questions of users. Advanced JQL usage often jira query language involves combining multiple conditions within a single query. You can do this using logical operators such as ‘AND’, ‘OR’, and ‘NOT’. In addition to temporal functions, there are also functions for people.

More in Jira

For more information, check out the official Atlassian documentation. Let’s look at another example examining the incoming bugs for our project. We want to see any new critical or blocking bugs that have come in recently to see if recent checkins have decreased stability. Let’s take a look at a visual representation of a set of issues that get returned from JIRA.

Our final step will be to add an OR clause that will allow us to find issues that are either part of Version 1.0 or Version 2.0, or is marked as priority 1. First, we’ll use the fixVersion field with an IN keyword and a list of Versions. Next, we’ll combine this using an OR keyword with a clause to find priority 1 issues. This final priority clause is a simple field + operator + value clause. Jira Query Language (JQL) is a text-based search language for Jira.

Issues Linked to Filtered Issues

The value -1d evaluates to 1 day behind the current date when the query is run. As a result, the above query will return all issues that do not have an assignee and haven’t been updated in the past day. In this query the “is empty” statement only includes issues where the value of the assignee field is blank. As a result, the above query will return all issues that do not have an assignee that are at least one day old. Advanced search allows you to build structured queries using Jira Query Language (JQL) to search for issues within and across projects. Query results can be saved and used as filters and views across Jira (including boards).

In this case, you write not a specific date, but a period of time. The “-” or “+” sign determines whether the current value lies in the past or in the future. From this point of view, it is a translation of the search query that you created earlier in the standard search mode. Functions are powerful because they can react dynamically as the environment changes.

The search box

If users are added to the test-engineering group, this query will start including issues assigned to the new members. It’s a more flexible solution than using assignee in (user1, user2, user3). In this example the person filing the bug is stored in the reporter field.

This interface is far more powerful than the Search box, but still has some limitations. Simply put, it is a very wide net with holes that are not specifically sized for the fish you want to catch. We have covered some of the commands in the Advanced JQL search mode.

Basic JQL Search

When you see the value you’d like to select, you can use the arrow keys or mouse to select it. Let’s say you want to view all the work assigned to you using a JQL filter. However, you only work on two projects within your entire organization. For more tips and assistance with Atlassian tools, feel free to get in touch with our team.

A JQL query can easily find the issues that aren’t meeting the SLA. If you are a Jira user or administrator, you’ve likely explored the search feature to find specific issues or lists of issues. While some searches are simple, others can be complex and require knowledge of JQL (Jira Query Language). Jira’s advanced search functionality allows you to refine your JQL queries further. In this query the “is empty” statement tells JIRA to return only issues where the value of the assignee field is blank.

The first query searches through all of the issues in your site to find the ones assigned to you. A JQL query can easily find the issues that are not meeting that SLA. You can also search issues from the “Issues” section in the dropdown menu. The “Current User” context can be used with specific fields/custom fields like Reporter, Assignee, Watcher, Voter, and Any User Picker custom field. Break down complex queries into simpler saved filters and combine them.

With ScriptRunner you can also not only use more JQL values but create your own as well. Actonic has also developed an app called Power JQL, with additional JQL functions to be used for the extended search. The “in” keyword will include any item that matches any item in the list. The most simple search feature in Jira is the search box at the top right of your screen. You can create custom widgets based on JQL searches and display them on your dashboard, making it easier to track and monitor your work across projects.

C. Using Saved Filters

Jira Query Language, fondly abbreviated to Jira JQL, is an exceptionally flexible query language created by Atlassian specifically for Jira software. This language is designed to help users construct precise search queries to sift through the multitude of issues within their projects. If you’ve ever worked with SQL (Structured Query Language) for database management, you’ll find JQL very familiar. For a complete reference, check out our help docs on advanced searching.

• Since we want items that meet all three criteria, we use the keyword “AND”, which means that the conditions to the left and right of AND have to be met.
• Use the blue bar at the top and click Issues→ Search for issues to get to the issue navigator.
• Let’s take a look at a visual representation of a set of issues that get returned from JIRA.
• The “in” keyword will include any item that matches any criteria in the list.
• For this part, we’ll use the “description” field combined with two keywords (IS NOT, EMPTY).
• Parentheses are an important piece of syntax to ensure the proper order of operations within a JQL statement.