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.
- What the sorting does is show us the most recent issues first.
- However, you only work on two projects within your entire organization.
- If your site has 10,000 issues Jira can look at the 500 issues in those projects and can ignore the remaining 9,500.
- Here, you can combine multiple fields, operators, and values using an intuitive dropdown system.
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.
C. JQL operators
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.
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.
Tips for Using Jira Query Language Like a Pro
You can also use “NOT IN” to identify everything that falls outside that query. In basic searches, the queries are already pre-built for you. JQL is also getting better, especially ever after the Jira 8.0 release.
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.
📖 Jira JQL Searching for what you need in Jira like Pro Jira Guru
It can often be overwhelming to start with a long and complex query when performing your search. So you could just start with a wide search and narrow down from there. A function is a pre-made command that users can plug into their query to return certain values. The rest of the query remains the same, except for the addition of an “OR” keyword and a query for high priority issues. For this example, let’s say we want to find all issues that are urgent and not done within a specific Epic link.
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”. In addition to temporal functions, there are also functions for people. We have already come across the currentUser, which stands for the user who is currently logged in. If you double-click on “project”, you will see a drop-down menu where you can choose one of the possible fields.
Smart JQL Tricks
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.
Let’s look at another example examining the incoming bugs for our project. Let’s take a look at a visual representation jql query of a set of issues that get returned from JIRA. This result is better, but you can narrow it down even more.
Operators in Jira Query Language
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.
Like in math class, functions boil down complex logic and make it easy for you to access and use in a simple way. Regularly review saved filters to ensure they are still relevant and performing well. Use the ~ operator to perform a text search within fields.
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.
