“watcher” – allows you to see which issues specific individuals are tracking while “voter” and “votes” have equivalent functions.“watchers” – track issues by the number of people watching them, for example, “watchers > 10”.“worklogAuthor” – search for issues by the users who have logged work against them, for example, “worklogAuthor = “Francis””.“worklogDate” – find issues that have comments in work log entries within specific date ranges, for example, “worklogDate > “2″”.Operators are mathematical signs like equals (=), doesn’t equal (!=), greater than (>), less than or equal ( 25” (where more than 25% of the work is complete) They’re essentially what you’re looking for in relation to your fields.įor example, possible values for the Priority field would be: You can view a list of all fields in Jira’s documentation. Fields in Jira Query LanguageĪ field is a piece of information that describes issues – this is what you fill in when you use basic searches. Whereas you’ll have to write them from scratch in JQL.Īll queries are made up of fields, operators, values, and keywords. In basic searches, the queries are already pre-built for you. Breaking Down a JQL QueryĪ JQL query is a set of words and operators that define how Jira will narrow your search. With Advanced Searching, you’ll be forming your own JQL queries. However, you’ll reach their limitations pretty quickly, since you are limited by the existing forms. They’re quick to fill in and easy to use. Basic vs Advanced Searching in Jiraīasic searches in Jira are useful up to a certain point. This is where you’ll have access to Jira JQL. You’ll notice the “Advanced” option to the right of the filters: Which you can use to filter issues using predefined fields like: By default, this screen brings you to the basic search tool. Under “Issues” in the dropdown menu, you can find the “Search for Issues” option: Overview of Jira Query Language Interface Now running JQL searches 33% faster than Jira 7.12 and almost entirely eliminating memory issues previously faced when making complex searches. JQL is also getting better, especially ever after the Jira 8.0 release. This would tell you how many issues were out of scope in the last sprint and couldn’t be completed. You could narrow your search for issues that are not closed in the current sprint AND that were previously assigned to another sprint. Or let’s say you needed to figure out if your project has scoping problems. And, in turn, helps you find what you’re looking for much faster:įor example, if you wanted to find all unplanned issues, you could search for issues with a status field that is not closed, and with empty fields for epic links and fix versions. The system uses the following data to filter issues. Jira Query Language (or JQL) is one of the most powerful tools available in Jira. In this guide, we’ll walk you through all the fundamental concepts you need to know to master JQL and become a pro Jira searcher. For example, if you want to find all issues assigned to yourself, just enter “my” in the search bar or type “r:me” to find all issues that you’ve reported. Even non-technical users can get the hang of it when guided in the right direction. However, this tool was designed so that anyone can benefit from its features. It sure was to me when I first started using Jira! Terms like operators and keywords can sound a bit frightening to less technical employees. Many non-technical Jira users tend to shy away from using JQL to its full potential. But effective query writing skills can also be quite helpful to other members of the team. Power users who employ Jira on a daily basis may already have a grasp of the Jira query language. Knowing how to search your Jira instance effectively can literally save you hours of work. 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.
0 Comments
Leave a Reply. |