
Search for tasks in JIRA (simple language). Part 2: Advanced Search
The structure of JQL queries without examples is difficult to understand for specialists who are not familiar with JIRA before.
We already managed to tell you about a quick and basic search. Now let's move on to the most powerful of the three methods - advanced search.
In this mode, you can specify criteria that cannot be set in the other previous two modes (for example, ORDER BY sorting). But you have to master the creation of structured queries using the JIRA Query Language (JQL).

To use the "advanced" search go to the menu item Search -> Search queries.
And if you are in the "basic" search mode, click the "Advanced" button


1. Creating JQL queries
The simplest JQL query consists of a field followed by an operator, and then one or more valid values for this field. For example:
project = “YAT”
Such a query will help to find all the tasks of the “YAT” project. The project field is used here, the equivalent operator is "=", and the valid value is "YAT".
A more complex query might look like this:
project = “YAT” AND assignee = currentuser ()
So we will select all the tasks of the “YAT” project assigned to the current user
(that is, to you). The request contains: the logical operator "AND", the field "assignee" for selecting tasks by the current user, the equivalent operator "=" and the function "currentuser ()", which returns the name of the current user of the system.
When creating a query in the advanced search mode, JIRA displays a list of all possible operators for the query field.
JIRA also shows a list of available values for the " AffectedVersion ", " FixVersion ", " Components " fields, custom " Version " format fields and drop-down lists.
When used in a searchable format fields " the User " JIRA allows you to find the desired user by his name.
You can use parentheses in complex JQL queries. For example, if you want to find all the allowed tasks in the SysAdmin project, as well as all the tasks (of any status, any project) currently assigned to the system administrator (admin), you can use parentheses to indicate the priority of logical operators in the request.
(project = SysAdmin AND status = resolved) OR assignee = admin
Attention!
JQL has reserved characters.
If you want to use one of them in the request, you must:
Example:
summary ~ "\\ [example \\]"
Warning!
JIRA also has reserved words.
If one of the following words is mentioned in the search text, this text must be either double quotation marks ("......") or single ('......').
List of reserved words:
2. Using patterns for text search
Special characters can be used to define text search patterns. Let's look at a few examples:
3. JQL logical operators
4. JQL comparison operators
5. JQL Functions
I hope that the analysis of the advanced mode will help you in finding tasks.
Use and do not get lost;)
We already managed to tell you about a quick and basic search. Now let's move on to the most powerful of the three methods - advanced search.
In this mode, you can specify criteria that cannot be set in the other previous two modes (for example, ORDER BY sorting). But you have to master the creation of structured queries using the JIRA Query Language (JQL).

To use the "advanced" search go to the menu item Search -> Search queries.
And if you are in the "basic" search mode, click the "Advanced" button


1. Creating JQL queries
The simplest JQL query consists of a field followed by an operator, and then one or more valid values for this field. For example:
project = “YAT”
Such a query will help to find all the tasks of the “YAT” project. The project field is used here, the equivalent operator is "=", and the valid value is "YAT".
A more complex query might look like this:
project = “YAT” AND assignee = currentuser ()
So we will select all the tasks of the “YAT” project assigned to the current user
(that is, to you). The request contains: the logical operator "AND", the field "assignee" for selecting tasks by the current user, the equivalent operator "=" and the function "currentuser ()", which returns the name of the current user of the system.
When creating a query in the advanced search mode, JIRA displays a list of all possible operators for the query field.
JIRA also shows a list of available values for the " AffectedVersion ", " FixVersion ", " Components " fields, custom " Version " format fields and drop-down lists.
When used in a searchable format fields " the User " JIRA allows you to find the desired user by his name.
You can use parentheses in complex JQL queries. For example, if you want to find all the allowed tasks in the SysAdmin project, as well as all the tasks (of any status, any project) currently assigned to the system administrator (admin), you can use parentheses to indicate the priority of logical operators in the request.
(project = SysAdmin AND status = resolved) OR assignee = admin
Attention!
JQL has reserved characters.
symbol | + | . | , | ; | ? | | | * | / | % | ^ | $ | # | @ | [ | ] |
If you want to use one of them in the request, you must:
- select the text containing the special character either with double quotes ("......") or single ('......');
- if the search text contains one of the characters listed below, then a double backslashe ("\\") is always preceded by it.
+ - & |! () {} [] ^ ~ *? \: - also, to maintain an effective search in JIRA, there are reserved English words (also known as 'stop words') that are ignored in JQL search. The list of such words:
“a”, “and”, “are”, “as”, “at”, “be”, “but”, “by”, “for”, “if”, “in”, “into "," Is "," it "," no "," not "," of "," on "," or "," such "," that "," the "," their "," then ", "There", "these", "they", "this", "to", "was", "will", "with"
Example:
summary ~ "\\ [example \\]"
Warning!
JIRA also has reserved words.
If one of the following words is mentioned in the search text, this text must be either double quotation marks ("......") or single ('......').
List of reserved words:
A | “Abort”, “access”, “add”, “after”, “alias”, “all”, “alter”, “and”, “any”, “as”, “asc”, “audit”, “avg " |
B | “Before”, “begin”, “between”, “boolean”, “break”, “by”, “byte” |
C | “Catch”, “cf”, “char”, “character”, “check”, “checkpoint”, “collate”, “collation”, “column”, “commit”, “connect”, “continue”, “count "," Create "," current " |
D | “Date”, “decimal”, “declare”, “decrement”, “default”, “defaults”, “define”, “delete”, “delimiter”, “desc”, “difference”, “distinct”, “divide "," Do "," double "," drop " |
E | "Else", "empty", "encoding", "end", "equals", "escape", "exclusive", "exec", "execute", "exists", "explain" |
F | “False”, “fetch”, “file”, “field”, “first”, “float”, “for”, “from”, “function” |
H | "Having" |
I | “Identified”, “if”, “immediate”, “in”, “increment”, “index”, “initial”, “inner”, “inout”, “input”, “insert”, “int”, “integer "," Intersect "," intersection "," into "," is "," isempty "," isnull " |
J | "Join" |
L | "Last", "left", "less", "like", "limit", "lock", "long" |
M | "Max", "min", "minus", "mode", "modify", "modulo", "more", "multiply" |
N | “Next”, “noaudit”, “not”, “notin”, “nowait”, “null”, “number” |
O | "Object", "of", "on", "option", "or", "order", "outer", "output" |
P | "Power", "previous", "prior", "privileges", "public" |
R | “Raise”, “raw”, “remainder”, “rename”, “resource”, “return”, “returns”, “revoke”, “right”, “row”, “rowid”, “rownum”, “rows " |
S | “Select”, “session”, “set”, “share”, “size”, “sqrt”, “start”, “strict”, “string”, “subtract”, “sum”, “synonym” |
T | “Table”, “then”, “to”, “trans”, “transaction”, “trigger”, “true” |
U | "Uid", "union", "unique", "update", "user" |
V | "Validate", "values", "view" |
W | “When”, “whenever”, “where”, “while”, “with” |
2. Using patterns for text search
Special characters can be used to define text search patterns. Let's look at a few examples:
Sign | Scope and description | Example |
---|---|---|
? | "?" used to replace a single character in a pattern. For example, the spelling of the words “text” and “test” is distinguished by one character. To search for both options, just set the template: te? T | summary ~ "te? t" |
* | "*" is used to replace zero or more characters in a text template . For example, to select the text “Windows”, “Win95” or “WindowsNT”, you can use the template: win * To select the text “Win95” or “Windows95” you can use the template: wi * 95 | summary ~ "wi * 95" |
~ | "~" can be used to specify fuzzy search patterns. In this case, the character "~" is substituted at the end of the desired word. For example, to find a term spelling similar to “roam,” use the pattern: roam ~ As a result, the words “foam” or “roams” can be found. | summary ~ "prox ~" |
3. JQL logical operators
Operator | Description | Example |
---|---|---|
AND | Logical operation "AND" connecting two or more conditions. Used to clarify the selection conditions. | project = "YAT" and status = "Open" - select all tasks of the "YAT" project in the "Open" status |
OR | Logical operation "OR", connecting two or more conditions. | reporter = demo_1 or reporter = demo_2 - select all project tasks authored by user demo_1 or user demo_2. |
NOT | To reverse the result of a logical condition. | not assignee = demo_1 - select all tasks whose executor is not the user demo_1. |
ORDER BY | Sort by. By default, the custom order used for this field will be used . You can override the sort direction - ascending ("asc") or descending ("desc"). | duedate = empty order by created - select all tasks for which “Due date” fields are empty, sort the selection results by the “Created” field. duedate = empty order by created, priority desc - select all tasks that have empty “Due date” fields, sort the results of the selection by the “Created” field in its own order, then by the “Priority” field (Priority) ) in descending order. |
4. JQL comparison operators
Operator | Description | Example |
---|---|---|
= | Equivalent. Used to set the criteria for full compliance. | reporter = demo_1 |
! = | Not equal. It is used to set a search criterion that unambiguously says that in a found task a certain field should not contain a certain value. | reporter! = demo_1 or you can use the entry NOT reporter = demo_1 |
> | More than. Used to create expressions with fields of the “Version” format , a date-time format, and numeric fields. | votes> 4 duedate> now () |
> = | More than or equal. Used to create expressions with fields of the “Version” format , a date-time format, and numeric fields. | votes> = 4 duedate> = "2008/12/31" created> = "-5d" |
< | Less than. Used to create expressions with fields of the “Version” format , a date-time format, and numeric fields. | votes <4 duedate <now () |
<= | Less than or equal. Used to create expressions with fields of the “Version” format , a date-time format, and numeric fields. | updated <= "-4w 2d" |
IN | Used to select tasks by the presence of one of the values in a specific field. A set of value variants is highlighted on both sides by parentheses; variants inside the brackets are listed with a comma. | affectedVersion in ("3.14", "4.2") reporter in (demo_1, demo_2) or assignee in (demo_1, demo_2) |
NOT IN | It is used to select tasks in a certain field which do not contain any of the listed values. A set of value variants is highlighted on both sides by parentheses; variants inside the brackets are listed with a comma. | FixVersion not in (A, B, C, D) or you can use the not fixVersion in (A, B, C, D) entry |
~ | Contains. Used exclusively for selection criteria for text fields. | summary ~ win summary ~ "issue collector" |
! ~ | Does not contain. Used exclusively for selection criteria for text fields. | summary! ~ “issue collector” or you can use the not summary ~ “issue collector” entry |
IS | This operator can only be used with EMPTY or NULL values. Used to search for tasks whose specific field does not contain values. | fixVersion is empty |
IS NOT | This operator can only be used with EMPTY or NULL values. It is used to search for tasks whose specific field is required. | affectedVersion is not empty |
Was | For the selection of tasks, a specific field which previously had the specified value. Applicable exclusively to fields:
The WAS operator may also have the following optional predicates:
| status WAS “In Progress” - for selecting tasks that have ever been in the status of “In Progress”. status WAS “Resolved” BY demo_1 BEFORE “2011/02/02” - to select tasks transferred to the “Resolved” status by the user demo_1 before the date “2011/02/02”. |
Was in | To select tasks whose specific field previously contained one of the listed values. The scope and predicates used for the WAS IN operator are the same as for the WAS operator. | status WAS IN (“Resolved”, “In Progress”) BEFORE “2011/02/02” - to select tasks transferred to the status “Resolved” or “In Progress” before the date “2011/02/02”. |
Was not in | For the selection of tasks that never, or until some point, did not contain any of the listed values in a certain field. The scope and predicates used for the WAS NOT IN operator are the same as for the WAS operator. | status WAS NOT IN (“Resolved”, “In Progress”) BEFORE “2011/02/02” - for selecting tasks that were not previously in the “Resolved” and “In Progress” status until the date “2011/02/02”. |
Was not | To select tasks that never, or until some point, did not contain a given value in a specific field. The scope and predicates used for the WAS NOT operator are the same as for the WAS operator. | status WAS NOT “In Progress” BEFORE “2011/02/02” - to select tasks that were not previously in In Progress status until the date “2011/02/02”. |
CHANGED | To select tasks whose specified field has been changed. Applicable exclusively to fields:
The WAS operator may also have the following optional predicates:
| assignee CHANGED - to select tasks whose executor has been changed. status CHANGED FROM “In Progress” TO “Open” - to select status tasks that have been changed from “In Progress” back to “Open”. priority CHANGED BY demo_1 BEFORE endOfWeek () AFTER startOfWeek () - to select tasks whose priority was changed by demo_1 during the current week. |
5. JQL Functions
Function | Description | Syntax | Available Operators | Examples |
---|---|---|---|---|
approved () | Only for JIRA Service Desk. To select JIRA Service Desk tasks requiring approval, the final decision on which is approved. Applies to fields of type "Approvals". | approved () | = | approval = approved () |
approver () | Only for JIRA Service Desk. To select JIRA Service Desk tasks requiring approval or already agreed upon by one or all of the specified users. Applies to fields of type "Approvals". | approver (user, user) | = | approval = approver (demo_1, demo_2) |
cascade Option () | For the selection of tasks by the value of the cascading field (fields of dependent lists). | cascadeOption (parentOption) cascadeOption (parentOption, childOption) | IN, NOT IN | “Request Type” in cascadeOption (“Developer”, “Prolongation”) |
closed Sprints () | Applicable to the Sprint field. To select tasks added to completed sprints. | closedSprints () | IN, NOT IN | sprint in closedSprints () |
components LeadByUser () | Applicable to the "Components" field. To select tasks in the “Components” field of which a component is selected whose leader you are or the user of your choice. | Components LeadByUser () is used to select tasks for the current user components LeadByUser (username) | IN, NOT IN | component in components LeadByUser () - you are the leader of the components . component in components LeadByUser (demo_1) - the leader of the components is the user demo_1. |
current Login () | Returns the session time of the current user. It is used in expressions with the fields “Created”, “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | currentLogin () | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | created> currentLogin () |
currentUser () | Returns the login of the current authorized user. Used to create expressions with the fields “Reporter” (Author), “Assignee” (Artist), “Voter”, “Watcher” and custom fields of the “User” format. | currentUser () | =,! = | reporter = currentUser () assignee! = currentUser () OR assignee is EMPTY |
earliest Unreleased Version () | To search based on the earliest unreleased version (i.e. the next version to be released) of the specified project. Caution The earliest unreleased version is determined by order, not dates. It is used to create expressions with the fields "AffectedVersion" (Appears in versions ")," FixVersion "(Fixed in versions), custom fields of the Version format. | earliest Unreleased Version (project) | IN, NOT IN | affectedVersion = earliestUnreleased Version (ABC) fixVersion = earliestUnreleased Version (ABC) |
endOfDay () | To search by the end of the current day . Used in expressions with the fields “Created”, “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | endOfDay () endOfDay ("inc") where inc is the optional increment (±) nn (y | M | w | d | h | m). If the time unit specifier is omitted, the default is to use the natural period of the function, i.e. 1 day. If the ± sign is omitted, then the default is +. | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | due <endOfDay () - due date until the end of the current day. due <endOfDay ("+1") - due date until the end of tomorrow. |
endOfMonth () | To search by the end of the current month . It is used in expressions with the fields “Created”, “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | endOfMonth () endOfMonth ("inc") where inc is the optional increment (±) nn (y | M | w | d | h | m). If the time unit specifier is omitted, the default is to use the natural period of the function, i.e. 1 month. If the ± sign is omitted, then the default is +. | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | due <endOfMonth () - due date until the end of the current month. due <endOfMonth ("+ 15d") - due date until the 15th day of the next month. |
endOfWeek () | To search by the end of the current week . It is used in expressions with the fields “Created”, “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | endOfWeek () endOfWeek ("inc"), where inc is the optional increment (±) nn (y | M | w | d | h | m). If the time unit specifier is omitted, the default is to use the natural period of the function, i.e. 1 week. If the ± sign is omitted, then the default is +. | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | due <endOfWeek () - due date until the end of the current week. due <endOfWeek ("+1") - due date until the end of next week. |
endOfYear () | To search by the end of the current year . It is used in expressions with the fields “Created” , “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | endOfYear () endOfYear ("inc") where inc is the optional increment (±) nn (y | M | w | d | h | m). If the time unit specifier is omitted, the default is to use the natural period of the function, i.e. 1 year. If the ± sign is omitted, then the default is +. | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | due <endOfYear () - due date until the end of the current year. due <endOfYear ("+ 3M") - due date until the end of March next year. |
issueHistory () | Returns the last 50 tasks you viewed. | issueHistory () | IN, NOT IN | issue in issueHistory () |
issuesWith RemoteLinks ByGlobalId () | For selecting tasks that have external links with specific global ids. Warning The function allows you to enter global id identifiers in an amount from 1 to 100. An empty function call or a function call with the number of parameters > 100 will result in an error . | issues WithRemote LinksByGlobalId () | IN, NOT IN | issue in issuesWithRemote LinksByGlobalId (abc, def) |
lastLogin () | Returns the start time of the previous session of the current user. It is used in expressions with the fields “Created”, “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | lastLogin () | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | created> lastLogin () |
latest Released Version () | To search based on the latest released version of the specified project. Caution The most recent version released is determined by order, not dates. It is used to create expressions with the fields "AffectedVersion" (Appears in versions), "FixVersion" (Fixed in versions), custom fields of the Version format. | latest ReleasedVersion (project) | =,! = | affectedVersion = latestReleased Version (ABC) fixVersion = latestReleased Version (ABC) |
linkedIssues () | To select tasks based on the presence of a connection with a specific task. Attention LinkType is case sensitive. | linkedIssues (issueKey) linkedIssues (issueKey, linkType) | IN, NOT IN | issue in linkedIssues (ABC-123, "is duplicated by") |
membersOf () | To select tasks based on user belonging from a specific field to a specific JIRA group. Used to create expressions with the fields “Reporter” (Author), “Assignee” (Artist), “Voter”, “Watcher” and custom fields of the “User” format. | membersOf (Group) | IN, NOT IN | assignee not in membersOf (QA) |
myApproval () | Only for JIRA Service Desk. To select JIRA Service Desk tasks that require approval by the current user or already agreed by the current user. Applies to fields of type "Approvals". | myApproval () | = | approval = myApproval () |
myPending () | Only for JIRA Service Desk. To select JIRA Service Desk tasks that require approval by the current user. Applies to fields of type "Approvals". | myPending () | = | approval = myPending () |
now () | To search for the current time . Used to create expressions with the fields “Reporter” (Author), “Assignee” (Artist), “Voter”, “Watcher” and custom fields of the “User” format. | now () | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | duedate <now () and status not in (closed, resolved) |
openSprints () | Applicable to the Sprint field. To select tasks added to incomplete sprints | openSprints () | IN, NOT IN | sprint in openSprints () |
pending () | Only for JIRA Service Desk. For selection of JIRA Service Desk tasks requiring approval. Applies to fields of type "Approvals". | pending () | = | approval = pending () |
pendingBy () | Only for JIRA Service Desk. To select JIRA Service Desk tasks that require the approval of the specific user (s). Applies to fields of type "Approvals". | pendingBy (user1, user2) projectsLead ByUser () | = | approval = pending (demo_1) approval = pending (demo_1, demo_2) |
projectsLead ByUser () | To select tasks from projects that have a specific user assigned to the Project Lead role. Applies to the Project field. | projectsLeadByUser () - for selecting tasks by the current user. projectsLead ByUser (username) | IN, NOT IN | project in projectsLead ByUser () AND status = Open project in projectsLead ByUser (demo_1) AND status = Open |
projects WhereUser Has Permission () | To select tasks from projects in which the current user has a specific permission . Applies to the Project field. | projects WhereUser HasPermission (permission) | IN, NOT IN | project in projectsWhere UserHas Permission ("Resolve Issues") AND status = Open |
projects WhereUser HasRole () | To select tasks from projects in which the current user has a specific project role . Applies to the Project field. | projectsWhere UserHasRole (rolename) | IN, NOT IN | project in projectsWhere UserHasRole ("Developers") AND status = Open |
released Versions () | To search by released versions of a specific project or all JIRA projects at once. It is used to create expressions with the fields "AffectedVersion" (Appears in versions), "FixVersion" (Fixed in versions), custom fields of the Version format. | ReleasedVersions () - for selecting tasks for all projects. releasedVersions (project) | IN, NOT IN | fixVersion in releasedVersions (ABC) affectedVersion in releasedVersions (ABC) |
standard IssueTypes () | For selecting tasks of the parent type. | standard IssueTypes () | IN, NOT IN | issuetype in standard IssueTypes () |
startOf Day () | To search by the beginning of the current day . It is used in expressions with the fields “Created” , “Due Date” , “Resolved” , “Updated”, custom fields of the date-time format. | startOfDay () startOfDay ("inc") where inc is the optional increment (±) nn (y | M | w | d | h | m). If the time unit specifier is omitted, the default is to use the natural period of the function, i.e. 1 day. If the ± sign is omitted, then the default is +. | =,! =,>,> =, <, <= in the predicates of the operators WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | created> startOfDay () - tasks created for the current day. created> startOfDay ("-3d") - tasks created in the last three days. |
startOf Month () | Для поиска по началу текущего месяца. Используется в выражениях с полями «Created» (Создано), «Due Date» (Срок исполнения), «Resolved» (Дата решения), «Updated» (Обновлено), кастомными полями формата дата-время. | startOfMonth() startOfMonth(«inc») где inc — опциональный инкримент (±)nn(y|M|w|d|h|m). Если спецификатор единицы измерения времени опущен, по умолчанию используется естественный период функции, т. е. 1 месяц. Если опущен знак ±, то по умолчанию предполагается +. | =, !=, >, >=, <, <= в предикатах операторов WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | created > startOfMonth() — задачи, созданные за текущий месяц created > startOfMonth ("+14d") — задачи, созданные с пятнадцатого числа текущего месяца. |
startOf Week() | Для поиска по началу текущей недели. Используется в выражениях с полями «Created» (Создано), «Due Date» (Срок исполнения), «Resolved» (Дата решения), «Updated» (Обновлено), кастомными полями формата даты-времени. | startOfWeek() startOfWeek(«inc»), где inc — опциональный инкримент (±)nn(y|M|w|d|h|m). Если спецификатор единицы измерения времени опущен, по умолчанию используется естественный период функции, т. е. 1 неделя. Если опущен знак ±, то по умолчанию предполагается +. | =, !=, >, >=, <, <= в предикатах операторов WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | created > startOfWeek()- задачи, созданные за текущую неделю. created > startOfWeek ("-1") — задачи, дата создания которых старше начала прошлой недели. |
startOf Year() | Для поиска по началу текущего года. Используется в выражениях с полями «Created» (Создано), «Due Date» (Срок исполнения), «Resolved» (Дата решения), «Updated» (Обновлено), кастомными полями формата дата-время. | startOfYear() startOfYear(«inc») где inc — опциональный инкримент (±)nn(y|M|w|d|h|m). Если спецификатор единицы измерения времени опущен, по умолчанию используется естественный период функции, т. е. 1 год. Если опущен знак ±, то по умолчанию предполагается +. | =, !=, >, >=, <, <= в предикатах операторов WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED | created > startOfYear() — задачи созданные за текущий год. created > startOfYear ("-1") — задачи, дата создания которых старше начала прошлого года. |
subtask IssueTypes() | Для отбора подзадач. | subtask IssueTypes() | IN, NOT IN | issuetype in subtask IssueTypes() |
unreleased Versions() | Для поиска по не выпущенным версиям определенного проекта или сразу всем JIRA-проектам. Применяется для создания выражений с полями «AffectedVersion» (Проявляется в версиях), «FixVersion» (Исправлено в версиях), кастомными полями формата Version. | unreleasedVersions() используется для отбора задач по всем проектам. unreleased Versions (project) | IN, NOT IN | fixVersion in unreleased Versions(ABC) |
voted Issues() | Для отбора задач, за которые вы отдали свой голос. | votedIssues() | IN, NOT IN | issue in votedIssues() |
watched Issues() | Для отбора задач, наблюдателем которых являетесь вы. | watchedIssues() | IN, NOT IN | issue in watchedIssues() |
I hope that the analysis of the advanced mode will help you in finding tasks.
Use and do not get lost;)