Note that the Lucene value for Request Type, is portal-key/request-type-key. While the portal key cannot be changed after a service project portal is created, the project key can be changed. The Request Type key cannot be changed once the Request Type is created. Search for issues that have a particular link type, like blocks or is duplicated by. You can only find issues from the Jira instance you’re searching on; remote links to issues on other Jira instances won’t be included. Search for issues that have open pull requests on linked Bitbucket instances.
Copy and paste fields, operators and functions into the Jira search bar, as well as learn more advanced queries. As an Atlassian partner we’ve done so in the past with multiple customers through JQL consultations or training sessions. This query will return all resolved issues from the Teams in Space project (clauses grouped by AND), and also all jql query existing issues assigned to captainjoe. This query will find all issues in the TEST project where the assignee is the currently logged in user. It uses the project field, the EQUALS operator, the value TEST,the AND keyword and the currentUser() function. Search for requests that were created on, before, or after a particular date (or date range).
JQL: the most flexible way to search Jira
Different projects may have versions with the same name. Note, it is safer to search by custom field ID than by custom field name. It is also possible for your Jira administrator to change the name of a custom field, which could break any saved filters that rely on that name. Custom field IDs, however, are unique and cannot be changed.
- Let’s take a look at a visual representation of a set of issues that get returned from JIRA.
- A JQL query can easily find the issues that are not meeting that SLA.
- JIRA gives suggestions at each step of the way for each of the three components of our query.
- Note, it is safer to search by priority ID than by priority name.
When searching JIRA, it’s easy to perform searches that return too many issues. In the above example both diagrams have the same number of issues we care about (issues with A on them) but the first query isn’t specific enough. Development managers often have to find areas of risk in their programs. Good queries often take a bit of refinement as they get developed. Let’s see if we can find some risky areas in our project PWC.
development[pullrequests].open
For example, add a red stripe to issues that have some blockers, and keep all other issues green. This will help you bring the right information to your team’s attention, at a glance. As of February 2024, Epic link function has been retired in favor of Parent. Existing filters that use the Epic link function still function, but you’ll need to use Parent when creating new filters. Search for issues that have successful and unsuccessful deployments on Bamboo instances. The “WAS NOT” operator is used to find issues that have never had the specified value for the specified field.
It is possible for your Jira administrator to change the name of a priority, which could break any saved filter that rely on that name. Priority IDs, however, are unique and cannot be changed. It is possible for your Jira administrator to change the name of a type, which could break any saved filter that rely on that name.
Introduction to JQL: Standard & advanced search in Jira
In our example, the units are linked logically with the AND keyword. Search for issues that are assigned to a particular affects version(s). You can search by version name or version ID (i.e. the number that Jira automatically allocates to a version). Note, it is better to search by version ID than by version name.
You can search by project name, by project key or by project ID (i.e. the number that Jira automatically allocates to a project). Search for issues tagged with a label or list of labels. You can also search for issues without any labels to easily identify which issues need to be tagged so they show up in the relevant sprints, queues or reports. Note that the Lucene value for Customer Request Type, is portal-key/request-type-key .
Request last activity time
The operator is followed by one or more values or functions. The operator compares the value of the field on the left side with one or more values or functions on the right side. The “WAS IN” operator is used to find issues that currently have or previously had any of multiple specified values for the specified field. This page describes information about operators that are used for advanced searching. You can search by issue level security name or issue level security ID (i.e. the number that Jira automatically allocates to an issue level security). If you double-click on “project”, you will see a drop-down menu where you can choose one of the possible fields.
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. For more information on fields, operators, keywords and functions, see the Reference section.
Less than equals (
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. As you can see in this example, parentheses can turn our example JQL query around. This query would return resolved issues that either belong to the Teams in Space project or are assigned to captainjoe. Using search in Jira can help you gain key project insights and answer questions that are relevant to the team.
Search for issues that belong to a particular component(s) of a project. You can search by component name or component ID (i.e. the number that Jira automatically allocates to a component). It is also possible to display all the issues that have been created in the last 10 days, for example. In this case, you write not a specific date, but a period of time.
In this example the person filing the bug is stored in the reporter field. JIRA also has a project field that matches the issue key. For example, the issue PIPELINE-2 is in the PIPELINE project. Again, we can set up multiple conditions joined by the AND keyword.
