April 22, 2019 at 16:53Search for tasks in JIRA (simple language). Part 1: Quick and Basic Search
Recently, JIRA is actively used by organizations that do not have a direct connection with IT. It is difficult for specialists who are not familiar with JIRA before to understand the structure of JQL queries if you do not give examples.
To simplify the perception, we decided to collect all the documentation, localize and place in one place. And we will start with the “basic” and “quick” searches.
Many were faced with the need to either find a suitable task in the variety of already created ones, or select a group of tasks that meet certain criteria. For this, JIRA provides flexible functionality designed for both a technical specialist and an ordinary user, and also allows you to save searches for later use. A saved request is called a filter.
There are three ways to search for tasks in JIRA:
In this article we will talk about the “basic” and “fast” search. How to use the "advanced" JQL search - we will tell in the next publication.
It is worth noting that, regardless of the selected search method, only the tasks available for your viewing will be returned as an answer. Accessibility is determined by access rights and security schemes in projects that own these tasks.
The least accurate and fastest way to find tasks in JIRA. The input field is located in the upper right corner of the screen. To use it, just start typing what you are looking for.
1. Quick transition to the task
If the key of the task you are working on is known, then to quickly jump, enter it and press Enter.
Suppose you are working on a task with the key "YAT-106", in this case, you can enter the value "YAT-106" or "yat-106" in the "Search" field.
Often you do not even need to enter the full key, just enter the digital part. If you are working on the “YAT” project, then when you enter in the “106” field, the system will automatically redirect you to “YAT-106”.
2. Intelligent quick search
JIRA allows you to use an “intelligent” fast search with minimal typing. For example, to search for all tasks of the “Task” type in the “YAT” project with the status “Done”, you need to search for the string “Task Done YAT”. And JIRA redirects you to the navigator window with tasks selected by the specified criteria.
The table below lists the specific terms for smart quick search:
3. Quick search by text
. You can also select tasks containing specific text - just enter it in the "Search" field. JIRA searches for tasks in the text in only three specific fields:
This is a convenient user interface for selecting tasks. To use it, you do not need to know the JIRA Query Language (JQL).
Go to the menu item Search → Search for queries ;
and select the search criteria:
By default, the "basic" search contains:
If you need to add some other field to the search criteria, then:
4. Check the box next to the required field;
5. Define the selection criteria for this field.
To delete an added selection criterion, simply use the button
for this criterion.
A query from a “base” search can be translated into an “advanced” JQL search, and vice versa. However, a query from an “advanced” JQL search cannot be translated into a “base” one if:
Внимание
Общее правило: если запрос не может быть создан в форме «базового» поиска, то его не получится перевести из «продвинутого» JQL в «базовый».
Об особенностях «продвинутого» JQL поиска поговорим в следующей статье ;)
To simplify the perception, we decided to collect all the documentation, localize and place in one place. And we will start with the “basic” and “quick” searches.
Many were faced with the need to either find a suitable task in the variety of already created ones, or select a group of tasks that meet certain criteria. For this, JIRA provides flexible functionality designed for both a technical specialist and an ordinary user, and also allows you to save searches for later use. A saved request is called a filter.
There are three ways to search for tasks in JIRA:
- Fast.
- Base.
- Advanced (JQL).
In this article we will talk about the “basic” and “fast” search. How to use the "advanced" JQL search - we will tell in the next publication.
It is worth noting that, regardless of the selected search method, only the tasks available for your viewing will be returned as an answer. Accessibility is determined by access rights and security schemes in projects that own these tasks.
Quick search
The least accurate and fastest way to find tasks in JIRA. The input field is located in the upper right corner of the screen. To use it, just start typing what you are looking for.
1. Quick transition to the task
If the key of the task you are working on is known, then to quickly jump, enter it and press Enter.
Suppose you are working on a task with the key "YAT-106", in this case, you can enter the value "YAT-106" or "yat-106" in the "Search" field.
Often you do not even need to enter the full key, just enter the digital part. If you are working on the “YAT” project, then when you enter in the “106” field, the system will automatically redirect you to “YAT-106”.
2. Intelligent quick search
JIRA allows you to use an “intelligent” fast search with minimal typing. For example, to search for all tasks of the “Task” type in the “YAT” project with the status “Done”, you need to search for the string “Task Done YAT”. And JIRA redirects you to the navigator window with tasks selected by the specified criteria.
The table below lists the specific terms for smart quick search:
| Search parameter | Description | Search string example |
|---|---|---|
| my | Search for tasks assigned to you. | my open task |
| r: | Search for tasks authored by you or another user, or the author is not defined. Caution There should be no spaces between “r:” and the author’s definition . | r: me - searches for tasks authored by you. r: demo_3 - search for tasks authored by a user with the username demo_3. r: none - search for tasks whose author is not set. |
or | Search for all tasks of a specific project by its name or key. | Yat project yat yat |
| overdue | The search for tasks whose deadline expires today, or has already ended. | overdue |
| created: updated: due: | Search for tasks whose date parameters “Created”, “Updated”, “Due Date” would meet the specified criteria. Accordingly, the “Created” parameter will correspond to “created”, “Updated” - “updated”, “Due Date” - “due”. When setting the terms, you can use the terms "today", "yesterday", "tomorrow". It is also possible to record the form “-1w”, “1w” indicating that the date of interest to us lies in the range from (-1 week) to (+1 week) from the current system time. A record of the form “1w” means that we are interested in date lies in the range from (+1 week) from the current system time. Valid abbreviations for date and time: 'w' (week), 'd' (day), 'h' (hour), 'm' (minute). | created: today - selection of tasks created for the current day. created: yesterday - tasks created yesterday. updated: -1w - tasks updated in the last week. due: 1w - the due date begins one week from the current date. due: -1d, 1w - the due date lies in the range from (<current date> - 1 day) to (<current date> + 1 week) created: -1w, -30m - the creation date lies in the range from (<current date date and time> - 1 week) until (<current date and time> - 30 minutes) created: -1d updated: -4h - tasks created for the last day and updated during the previous four hours. |
| Search for tasks by a given priority. | critical high medium low | |
| Search for tasks of a specific type. Caution You can use plural values. | bug task bugs tasks | |
| Search for tasks by the value of the “Resolution” field. | fixed duplicate | |
| c: | Search for tasks with a specific value for the “Component / s” field. Caution There should be no spaces between the “c:” and the component definition . | c: security - tasks in the name of the components of which contain the word "security". |
| v: | Searching for tasks by the value of the “Affects Version / s” field (Appears in versions) Warning There should be no spaces between “v:” and the version definition. | v: 3.0 - tasks are selected with values for the Affects Version / s field (Appears in versions): 3.0 3.0 eap 3.0 beta But it does not include tasks with the following values for the Affects Version / s field (Appears in versions): 3.0 .1 3.0.0.4 To select tasks that also contain minor and assembly versions, a record of the form is used: v: 3.0 * Tasks with values for the “Affects Version / s” field (“Appears in versions”) will be selected as a result of the run : 3.0 3.0 eap 3.0 beta 3.0.1 3.0.0.4 |
| ff: | Search for tasks by the value of the “Fix Version / s” field (Fixed in versions). The search for the parameter “ff:” is performed similarly to the search for the parameter “v:”. | ff: 3.0 ff: 3.0 * |
3. Quick search by text
. You can also select tasks containing specific text - just enter it in the "Search" field. JIRA searches for tasks in the text in only three specific fields:
- “Summary” (“Theme”);
- “Description”;
- "Comments" ("Comments").
Basic search
This is a convenient user interface for selecting tasks. To use it, you do not need to know the JIRA Query Language (JQL).
Go to the menu item Search → Search for queries ;
and select the search criteria:
By default, the "basic" search contains:
- The “Project” criterion from the drop-down list for selecting projects containing tasks of interest to you.
- Criterion "Task / Type" from the drop-down list to select the type of tasks.
- The “Status” criterion from the drop-down list for selecting tasks by workflow status.
- The criterion "Contractor" for the selection of tasks assigned to specific performers. As performers, you can select specific JIRA users, or a JIRA group (tasks assigned to this group will be displayed).
- The "Contains text" criterion for selecting tasks that may contain specific text in the "Summary", "Description", or "Comments" fields.
If you need to add some other field to the search criteria, then:
- First, we recommend defining the projects to search in the "Project" field;
- Define the type of tasks in the "Type" field;
- In the "More" drop-down list, start entering the name of the field that will be used as a selection criterion.
4. Check the box next to the required field;
5. Define the selection criteria for this field.
To delete an added selection criterion, simply use the button
for this criterion.
A query from a “base” search can be translated into an “advanced” JQL search, and vice versa. However, a query from an “advanced” JQL search cannot be translated into a “base” one if:
- the request contains an OR statement ;
- the request contains a NOT operator ;
- the request contains an EMPTY statement ;
- contains any of the comparison operators ! =, IS, IS NOT,>,> =, <, <= .
- в запросе указываются поля, которые в «базовом» поиске становятся доступными только после выбора критериев проекта и типа задач.
Внимание
Общее правило: если запрос не может быть создан в форме «базового» поиска, то его не получится перевести из «продвинутого» JQL в «базовый».
Об особенностях «продвинутого» JQL поиска поговорим в следующей статье ;)