What is advanced search?
Advanced search lets you search for JIRA issues using structured queries. The search results will be displayed in the issue navigator and you can export them to various formats such as MS Excel. You can also save and subscribe to your advanced searches.
When you perform an advanced search, you are using the JIRA Search Language (JQL). A JQL simple query (also called a "statement") consists of a field, including an operator, one or more values or functions. For example, the following simple query will search for all issues in the "TEST" project:
project = "TEST"
This example uses the Project field, the EQUALS operator, and the "TEST" value. 
JQL provides some SQL-like syntax, such as the ORDER BY SQL keyword and the ISNULL() SQL function. However, JQL is not a database query language. For example, JQL does not have a SELECT statement.
How to perform an advanced search
- Selecting Issues > Search for Issues will bring up the issue navigation screen.
- If there are existing search criteria, click the New filter button to reset the search criteria.
- If Advanced is displayed as a link, click the link to switch to Advanced Search.
- Enter query criteria using fields, operators, field values, or functions.
- Click the Search button to execute the query.
perform a text search
The CONTAINS operator of Lucene's text search functionality can be used when performing searches on the following fields:
- Summary
- Description
- Environment
- Comments
- custom fields take a "free text searcher" and include the following built-in custom field types:
- Free Text Field (unlimited text)
- Text Field (< 255 bytes)
- Read-only Text Field
Search for questions using the "some words" value of a text field in JQL. This searches all text custom fields like summary, description, context, comments. If you have a lot of text custom fields, you can improve your search by searching for specific fields, for example:
Summary ~ "some words" OR Description ~ "some words"
Use autocomplete
When you enter query criteria, JIRA will automatically recognize the context and provide a list of autocomplete suggestions. The autocomplete recommendation list is sorted alphabetically, including the top 15 matching values. Note that the autocomplete recommendation does not provide function parameters. Note:
If the autocomplete recommendation does not appear, it may be because your administrator has turned off this feature for the JIRA instance. The
autocomplete recommendation will not appear in all fields. Click Field Reference to see which fields support autofill.
Switch between advanced and simple search
Typically, a query created using "Simple Search" might be converted to "Advanced Search" (JQL), and then simply query the query.
However, queries created using Advanced Search will not be converted into Simple Search, especially when:
- Query contains OR operator (note you can use IN operator, but it will be converted, eg: project in (A, B))
- Example: Although (project = JRA OR project = CONF) query is equivalent to (project in (JRA, CONF)), only the second query will be transformed
- Query contains NOT operator
- Query contains EMPTY operator
- The query contains any !=, IS, IS NOT, >, >=, <, <= operators
- The query specifies fields and values in related projects (eg version, composition, custom fields), and that project is not explicitly included in the query (eg fixVersion="4.0" without AND project=JRA). These custom fields are especially tricky because they can be configured on a project/issue type basis. A general rule of thumb is that if the query cannot be created in a "simple search" form, then if the query is created using an "advanced search", then the query will not be converted to a "simple search".
set operator precedence
You can emphasize the precedence of operators in a JQL statement by using parentheses. For example, if you want to find all resolved issues in the SysAdmin project, as well as issues currently assigned to the sysadmin (bobsmith). You can use parentheses in your query to enforce boolean operator precedence, ie:
tatus=resolved AND project=SysAdmin) OR assignee=bobsmith
Note that if you don't use parentheses, the statement will use operator precedence level assessment. You can also use parentheses to group statements, which allows you to apply the NOT operator to groups. If you add parentheses to enforce precedence, but they execute without the strict operator precedence but return the same result, JIRA will remove the precedence from your query statement when you save the query.
More>> JIRA Chinese Tutorial