That way, you’ll have access to your search results with a single glance. When you click on “Advanced Search”, you’ll get a search bar with no pre-made filters. On the other hand, “OR” will return all issues that fulfill either of your conditions. Each keyword has a specific meaning that further narrows the search, like “AND” and “OR”.
Let’s look at another example examining the incoming bugs for our project. Let’s take a look at a visual representation of a set of issues that get returned from JIRA. This result is better, but you can narrow it down even more.
Select all issues you are interested in
And I cannot agree enough with @Evgenii regarding the use of parentheses – this has solved my issues more times than I can count. Jira Query Language is an invaluable tool for anyone using Jira. 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’.
For example, the issue PIPELINE-2 is in the PIPELINE project. Again, we can set up multiple conditions joined by the AND keyword. Using an AND would give only the area covered by both circles, but an OR returns all items in either circle.
Performing text searches
You are now on your way to creating more effective queries in Jira software to have a clearer view of your projects, teams, and work ahead. If you’ve not seen lesson 1, I’d suggest reviewing that post as we will build on a number of concepts talked about in that post. You should be comfortable with simple JQL queries as well as using the AND and OR keywords at this point. This query returns issues created from the start of the current month. A simple query in JQL (also known as a “clause”) consists of a field, followed by an operator, followed by one or more values or functions.
There is also an operator IS, which is used together with the keyword EMPTY (→ is or is not ). This checks whether a field is empty, i.e. without a value, or not. In other words, it allows you to search for issues that are not assigned to anyone. In the standard search, you can select values for different dropdown fields. On the other hand, JQL sorting will allow you to order the list of returned issues in a specific manner using the keyword “ORDER BY”. Jira’s Advanced Search page provides a user-friendly interface for building complex JQL queries.
Use advanced search with Jira Query Language (JQL)
It uses the project field, the EQUALS operator, the value TEST,the AND keyword and the currentUser() function. With the above search, you’ll get a very specific view of high or urgent priority issues that were carried over from the last sprint. You can do a great deal with fields, values, operators, and keywords.
You can even send your subscriptions to other users as well. However, there are many more features that will save you even more time and hassle. What’s really handy about Jira JQL is that it will auto-suggest as you type. This allows you to get the syntax right when you don’t know it by heart. If you need help referencing the syntax, you can always click on the question mark on the right of the search box.
What is JQL: functions, history, and sorting
A number of JQL fields are particularly useful for project tracking. Then you will get all resolved items from the Planning project as well as all resolved items assigned to Francis. You can then click on one of the suggested operators to continue building your JQL query. A JQL query can easily find the issues that are not meeting that SLA. These are my observations formed from current experience in answering the most frequent questions of users. To find out the version of Lucene Jira Software is using, go to /Installation-directory/atlassian-jira/WEB-INF/lib and locate the Lucene jar files.
- (Windows users will need to get curl.) If we want to grab all of the duplicate issues from the ANERDS project we could simply call the search REST endpoint.
- The query controls for priority and limiting the created time properly scope the query.
- The three flavors of search in Jira — quick, basic, and advanced — can help you find important information about your projects.
- Functions are powerful because they can react dynamically as the environment changes.
- Use the DESC keyword to sort in reverse (newest to oldest).
- For a complete reference, check out our help docs on advanced searching.
The smallest unit of a search query consists of a field which is compared by an operator with a field value or a function. The project field is compared with the SP field value using the “Is equal to” operator. The next unit compares the resolution field with the values ”Done” and “Unresolved”. The third unit checks the field assignee with the current user.
You can find saved searches (also known as Saving your search as a filter) in the left-side panel, when using advanced search. If the left panel is not showing, hover your mouse over the left side of the screen to display it. For more information on fields, operators, keywords and functions, see the Reference section. A simple query in JQL (also known as a “clause”) consists of a field, followed by an operator, followed by one or more values or functions. In general, a query created using basic search will be able to be translated to advanced search, and back again. However, sometimes a query created using an advanced search may not be able to be translated into a basic search.
But if you want to tap into complex logic that is easily accessible, you’ll need functions. Or let’s say you needed to figure out if your project has scoping problems. You could narrow your search for issues that are not closed in the current sprint AND that were previously assigned to another sprint. This would tell you how many issues were out of scope in the last sprint and couldn’t be completed. In this query the “is empty” statement only includes issues where the value of the assignee field is blank.
You can also use “NOT IN” to identify everything that falls outside that query. In basic searches, the queries jql query are already pre-built for you. JQL is also getting better, especially ever after the Jira 8.0 release.