The “WAS NOT” operator is used to find issues that have never had the specified value for the specified field. This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields only. The “WAS” operator is used to find issues that currently have or previously had the specified value for the specified field. ~ operator, the value on the right side of the operator can be specified by using Jira text-search syntax.
- As an Atlassian partner we’ve done so in the past with multiple customers through JQL consultations or training sessions.
- Consider that the “latest” is determined by the ordering assigned to the versions, not by actual Version Due Dates.
- Sharing filters allows others to use the same set of criteria to view issues.
- The WAS IN and WAS NOT IN operators allow using up to 3000 operands.
- Jira’s advanced search functionality allows you to refine your JQL queries further.
To meet user expectations, Atlassian Marketplace offers some additional apps with JQL functions. 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. Functions are special instructions that can be used in JQL queries to search for issues in a more dynamic or complex way.
JQL search in Jira Software
Search for issues that are assigned to a completed Sprint. Search for issues that required approval and have a final decision of approved. In addition to temporal functions, there are also functions for people.
Jira’s Advanced Search page provides a user-friendly interface for building complex JQL queries. Here, you can combine multiple fields, operators, and values using an intuitive dropdown system. The page also provides auto-complete suggestions, helping you avoid syntax errors and construct your queries more easily. We recommend switching to List View for a better overview. In this query the “is empty” statement only includes issues where the value of the assignee field is blank.
endOfDay()
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. A function in JQL appears as a word followed by parentheses, which may contain one or more explicit values or Jira fields. This query would return the same results with or without the parentheses. You can set precedence in your JQL queries by using parentheses. Parentheses will group certain clauses together and enforce precedence.
The CHANGED operator is used to find issues where the value of a specified field was changed. The WAS NOT operator is used to find issues that have never had a specified value for a specified field. The WAS operator is used to find issues that currently have or previously had a specified value for a specified field. Search for issues that have successful deployments on linked Bamboo instances. Let’s take a look at a visual representation of a set of issues that get returned from JIRA.
What are elements of a JQL query?
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’.
Search for issues that require or required approval by one or more of the listed users. This uses an OR operator, and you must specify the usernames. Some Jira apps can add additional functions to the advanced issue search.
Operators
For the endOfWeek() function, the result depends upon your locale. Returns issues that have an that has completed at least one cycle. Returns issues that whose most recent has missed its goal. Thank you for sharing, I saved this article for reference. These are my observations formed from current experience in answering the most frequent questions of users. Remember, the best way to learn JQL is by trying it out yourself.
As a result, the above query will return all issues that do not have an assignee that are at least one day old. To run a filter, such as New_issues, select the filter name. The JQL for the advanced search will be set, and the search results will be displayed. 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 IN and WAS NOT IN operators allow using up to 3000 operands. Using WAS NOT IN is equivalent to using multiple WAS_NOT statements, but is shorter and more convenient. That is, status WAS NOT IN (“Resolved”,”In Progress”) is the same as status WAS jql query NOT “Resolved” AND status WAS NOT “In Progress”. Using WAS IN is equivalent to using multiple WAS statements, but is shorter and more convenient. That is, status WAS IN (“Resolved”,”Closed”) is the same as status WAS “Resolved” OR status WAS “Closed”.
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. We have covered some of the commands in the Advanced JQL search mode. For more information, check out the official Atlassian documentation.
Suggestions and bugs
You can also search on the released versions of all projects, by omitting the project parameter. Perform searches based on issues that are linked to a specified issue. You can optionally restrict the search to links of a particular type. Find issues in components that are led by a specific user. You can optionally specify a user, or if the user is omitted, the current user (i.e. you) will be used.
