In the standard search, you can select values for different dropdown fields. It is possible to add system and custom fields via More. Sometimes you need to set a field value in many issues. With a JQL query, you can filter out the required issues and carry out the bulk change using Tools in the top right-hand corner. Typing “AND” in your query will return issues that match both conditions of your search. In basic searches, the queries are already pre-built for you.
- It allows you to search for different document types in the attachment of an issue, and more.
- For example, you can run this command in the terminal on the Macintosh or Linux workstation.
- 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.
It uses the project field, the EQUALS operator, the value TEST,the AND keyword and the currentUser() function. We also have a downloadable cheat sheet to keep close on hand as you perform searches with JQL. Copy and paste fields, operators and functions into the Jira search bar, as well as learn more advanced queries. Get the list of issues for the specific project with due date changes for the current week + updated by a specific user.
A JQL example for “OR” Keyword
But values for fields like assignee, priority, fix version, and status often change over the course of an issue’s lifecycle. JIRA stores each update an issue goes through, known as an issue’s change history. In this query the “is empty” statement tells JIRA to return only issues where the value of the assignee field is blank.
To see changes to these or any fields you have, you can try alternative solutions like Issue History for Jira. It is a diary of changes, and with available filters, you can search for the items you need. In the above query, Jira would return a list of issues sorted by assignee first, then sort by due date for all issues with the same assignee.
JQL-based archeology with history operators
When you see the value you’d like to select, you can use the arrow keys or mouse to select it. 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. The Lucene version number will be part of the filename.
This query also shows how JIRA supports relative dates. 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.
Consistent Filter Naming
For example, if you want to save money by looking for items on sale or store brand items, we can use this query. The query uses the issuetype field, the EQUALS operator, the value Bug,the AND keyword, the component field, and the IN operator. Find issues where the assignee is a specific user, and the status has changed from “Open” to “In Progress” within the last week. The “in” keyword will include any item that matches any item in the list.
Efficient as it may be, Jira has its limitations when it comes to some search queries. If you want to use the wildcard search not only for text fields but also for dropdown fields or label fields, then our PowerJQL plug-in jira query examples is just for you. It allows you to search for different document types in the attachment of an issue, and more. Start your free trial now and enjoy all the benefits of extended search functionalities.
Understanding the Basics
Break down complex queries into simpler saved filters and combine them. When saving filters for reuse, use clear and descriptive names. This query finds all issues where the summary and description contains words starting with “roadmap” and “log”.
Find issues where the status changed from In Progress to Done after some date. This query will show issues that had due dates in December 2023. A JQL query can easily find the issues that are not meeting that SLA.
Jira JQL: advanced search queries made easy
You can also use “NOT IN” to identify everything that falls outside that query. 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. This will return all of the issues that were fixed in that particular release. What if we want a list that always shows the issues fixed in the last release whenever it was run?
But effective query writing skills can also be quite helpful to other members of the team. To get the list of subtasks in Jira, use the object “Parent” and specify the parent issue key(s). Before we delve into JQL tricks, let’s explore the different ways you can perform an issue search in Jira. 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. This query performs better than using non-indexed fields.
Regularly Review and Clean Up Filters
That way, you’ll have access to your search results with a single glance. The rest of the query remains the same, except for the addition of an “OR” keyword and a query for high priority issues. For example, you can run this command in the terminal on the Macintosh or Linux workstation. (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. Once the query is complete, JIRA validates the JQL and lets us know the syntax is correct by the green check in the left and side of the text entry box. Note the Syntax Help link, which opens a reference page to the JQL language.
