Again, we can set up multiple conditions joined by the AND keyword. Effective project management requires specific metrics from the issue tracker relevant to your project. 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. The “WAS NOT IN” operator is used to search for issues where the value of the specified field has never been one of multiple specified values.

However, if you wanted to see all issues that meet all the above criteria or any bug whose title includes the word ‘Critical’ – the basic search won’t be of immediate help. As seen below, a Jira jql query can be broken down into small elements – fields, operators, values, keywords, functions & more. It goes beyond the basic search & lets you dig deeper into the data with advanced features such as operators, functions, customizations & more.

B. Advanced Search in Jira JQL

The most simple search feature in Jira is the search box at the top right of your screen. Remember, the best way to learn JQL is by trying it out yourself. So, don’t be afraid to experiment with different queries and see what results you get. The more you practice, the more comfortable you’ll become with JQL. 4) Function – Retrieves only the true results specified within the function and clause.

• First, while you’re looking for a specific detail in Jira, you’ve to start from the ‘search’ bar.
• To view a detailed information about keywords and how to use them for advanced searching, check out Keywords reference page.
• The value -1d evaluates to 1 day behind the current date when the query is run.
• Following keywords are available to use in Jira – AND, OR, NOT, EMPTY, NULL, ORDER BY.
• JQL, or Jira Query Language, is a flexible tool that allows you to search for issues in Jira and pinpoint exactly what you are looking for.

So more often than not, you will work with your colleagues in there. That’s where the workload of creating various JQL queries can be distributed amongst the team. This makes it easy to find the exact issues you are looking for, no matter how complex your search criteria may be. For a complete reference, check out our help docs on advanced searching. I recommend bookmarking this link – I find myself returning to it often to look up obscure queries. The docs page has a lot of content, so it’s helpful to do a “Ctrl/Cmd + F” so you can jump directly to a specific topic or keyword of interest.

JQL-based archeology with history operators

To view a detailed information about functions and how to use them for advanced searching, check out Functions reference page. To view a detailed information about keywords and how to use them jira query language for advanced searching, check out Keywords reference page. To view a detailed information about operators and how to use them for advanced searching, check out Operators reference page.

We also discussed the advantages of advanced search over basic search, highlighting its precision and flexibility. The advanced search allows you to build structured queries using the Jira Query Language (JQL) to search for issues. You can specify criteria that cannot be defined in the quick or basic searches. For example, you can use the ORDER BY clause to sort Jira issues either in descending or ascending order or narrow down your search results for the desired date range.

Explore Learning Resources and Certifications

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’. Operators are the link between fields and values in a JQL query. The fields you can use in your JQL queries will depend on your Jira configuration and the specific fields available in your instance. Mastering JQL is the key that unlocks the hidden vaults of productivity and efficiency within Jira, propelling your project management endeavors to unprecedented heights. JQL empowers you to cut through the noise in a landscape brimming with countless boards and issues, swiftly extracting the precise information you seek.

JQL knowledge is mainly required when you do an advanced search. Queries can be constructed using a combination of keywords, operators, fields, and values. These well-structured queries can be used to search for issues under specific categories, like, project name, issue type, status, assignee, priority, and more. To recap, in this guide you’ve learnt the nuts & bolts of Jira Query Language, a powerful tool for advanced searching in Atlassian Jira. The initial part of this guide was focused on the basic concepts. That’s where we explored fields, operators, values, keywords, and functions, the building blocks of JQL queries.

A JQL example for “OR” Keyword

Functions are powerful because they can react dynamically as the environment changes. 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). The JQL for the advanced search will be set, and the search results will be displayed. 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.

Using search in Jira can help you gain key project insights and answer questions that are relevant to the team. The three flavors of search in Jira — quick, basic, and advanced — can help you find important information about your projects. One of the key benefits of using JQL is that it allows you to find the issues that you need quickly and easily.

Sharing Your JQL Queries

Give your filter a meaningful name so you can easily identify it later. Simple, check the entire query below & notice how we have added the OR keyword, used brackets to combine two seemingly different criteria together. You can even create custom software that runs SQL queries to retrieve data and presents the information in intuitive ways. The query will return JSON which you can then process in your client application. Let’s look at another example examining the incoming bugs for our project.

That is, typing status WAS IN (‘Resolved’, ‘Closed’) is the same as typing status WAS “Resolved” OR status WAS “Closed”. This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields only. JQL provides several functions that can be very powerful when used correctly. Relative dates (-7d, startOfWeek()) keep your filters dynamic and up-to-date.

Basic vs Advanced Searching in Jira

The “WAS NOT” operator is used to find issues that have never had the specified value for the specified field. If you want to find issues that are linked to a particular issue, use the linkedIssues() function. This query finds all issues where the summary and description contains words starting with “roadmap” and “log”. I’ve added +2 to the endOfDay() function because I needed to find out what is due in two days.