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.
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). In this query the “is empty” statement tells JIRA to return only issues where the value of the assignee field is blank. 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.
development[builds].passing
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. If you’re a Jira admin, note that this list is hard coded in the JqlStringSupportImpl.java file. These words need to be surrounded by quotation marks (single or double) if you wish to use them in queries.
Parentheses will group certain clauses together and enforce precedence. This field is only available if time tracking has been enabled by your Jira administrator, and can only support the CONTAINS operator (“~”). Search and sort through your requests to ensure that you’re hitting your SLA goals. You can search for requests whose SLAs are in a certain state of completion, or that have a certain amount of time on their SLA clock.
Greater than equals (>=)
Search for issues that belong to projects in a particular category. 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. From this point of view, it is a translation of the search query that you created earlier in the standard search mode. Immediately after logging in, you can see a dashboard with different gadgets, most of which can be configured with the help of JQL filters. JQL filters are also used to determine which issues will be displayed on Kanban and Scrum boards. Visit the Jira product guide to learn more about JQL, advanced search with use cases, and more.
Search for issues that were last viewed on, before, or after a particular date (or date range). Search for issues that were created on, before, or after a particular date (or date range). With the help of JQL (Jira Query Language) the search can be set up effectively. This is essential for developers, but project managers, team leads and other users might benefit from knowledge in JQL as well. So it’s safe to say that ideally every team working with Jira is able to use the advanced search with JQL. Please note that the search results will be relative to your configured time zone (which is by default the Jira server’s time zone).
development[deployments].environment
Search for issues where the summary contains specific text using Jira text-search syntax. This function works for both team-managed and company-managed projects. In a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions). The operator compares the value of the field with one or more values or functions on the right, such that only true results are retrieved by the clause.
The “IS NOT” operator can only be used with EMPTY or NULL. That is, it is used to search for issues where the jql query specified field has a value. That is, it is used to search for issues where the specified field has no value.
Jira Software
These stages can have multiple statuses that you set for your custom workflow. You can search by custom field name or custom field ID (i.e. the number that Jira automatically allocates to an custom field). Efficient as it may be, Jira has its limitations when it comes to some search queries.
The most simple search feature in Jira is the search box at the top right of your screen. Thank you for sharing, I saved this article for reference. Now let’s see which issues got fixed in the last release. Using an AND would give only the area covered by both circles, but an OR returns all items in either circle. Generally speaking, AND will narrow your query and return fewer results, while using an OR broadens it and will return more results.
Less than equals (
For example, an issue may duplicate another issue or depend on the resolution of another issue. You can find detailed information about issue links in Configuring issue linking. The search is based on either the epic’s name, issue key, or issue ID (i.e. the number that Jira automatically allocates to an issue). Search for Issues matching a specific Customer Request Type in a service desk project. You can search for a Customer Request Type either by name or description as configured in the Request Type configuration screen.
- However, sometimes a query created using an advanced search may not be able to be translated into a basic search.
- Then you probably will have stumbled upon the search function in Jira.
- We use the DESC keyword to sort in reverse (newest to oldest) so we focus our attention on the most important issues first.
- Parentheses will group certain clauses together and enforce precedence.
- It is possible to add system and custom fields via More.
Use the blue bar at the top and click Issues→ Search for issues to get to the issue navigator. You can filter on any field available in Jira (depending on the selected project(s)). @Andrei Pisklenov _Actonic_, thank you for sharing this post! This is really helpful for new Jira users who want to learn about Jira’s JQL search capabilities. Thanks for sharing this article @Andrei Pisklenov _Actonic_ ! This is really very useful for any new Jira users looking for learning JQL search capabilities in Jira.
You can specify criteria that cannot be defined in the quick or basic searches. When searching issueLinkType, Jira searches all three properties. This is the case for the default “Blocks” link type, where the name and outward description are “blocks”.
