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.
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.
B. Advanced Search in Jira JQL
In the meantime, you should now have the skills necessary to find every elusive issue in your Jira sea, just as Captain Ahab found his white whale. The Advanced Search Issues screen has a built in tool for error checking and will visually tell you if the statement you have entered is invalid JQL. To the left of the statement, you’ll find either a green checkmark if your JQL is valid, or a red X if it is not. In addition, the Advanced Search Issues screen will provide useful error messages to guide you while debugging your statement.
- Development managers often have to find areas of risk in their programs.
- This introduction is only the proverbial tip of the JQL iceberg.
- In this case, you can switch to advanced search which offers you tons of possibilities for special search functions.
- The basic version of this tool allows a user to filter based on any available fields in their instance.
- Jira Query Language is an invaluable tool for anyone using Jira.
For example, the issue PIPELINE-2 is in the PIPELINE project. Again, we can set up multiple conditions joined by the AND keyword. Then you probably will have stumbled upon the search function in Jira. Be it while looking for a specific ticket, to automate workflows or to create reports.
Current User Context and User Membership Queries: Personalized Issue Searches using Jira JQL
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.
This is really very useful for any new Jira users looking for learning JQL search capabilities in Jira. If your site has 10,000 issues Jira can look at the 500 issues in those projects and can ignore the remaining 9,500. Fewer issues to sort through, the quicker the query can run, even though the results are the same. To get the list of subtasks in Jira, use the object “Parent” and specify the parent issue key(s). If you want to find issues that are linked to a particular issue, use the linkedIssues() function. Operators are the link between fields and values in a JQL query.
What is JQL?
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 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.
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.
Subtask Queries
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.
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.
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).
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.
Jira JQL: advanced search queries made easy
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 jira query language 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.
