Query constant #NULL - For querying objects with empty field values, you should no longer use the #NULL query constant. Example: targetRelease.KEY:2.1.0, and not targetRelease:2.1.0 For example, use: HAS_VALUE:targetRelease rather than CUSTOM_FIELDS:targetRelease.Īlso, custom fields of type enumeration now use the. Work Item field CUSTOM_FIELDS - Querying the HAS_VALUE field is preferred to the CUSTOM_FIELDS field. It is recommended that you update all such usages in saved queries, macro and page parameters in Wiki pages, API calls, etc. The same query language is applicable in a number of administrative tasks such as customization of configuration files that contain query expressions or elements or attributes that consist of a query expression.Įxisting queries that use any of the constructs mentioned below still work, but are now considered deprecated and long-term support for them is not guaranteed. To optimize the performance of your queries, consult the Apache Lucene Syntax Documentation. Using many parenthetical expressions in queries may negatively impact performance because more time is spent in query pre-processing. For example, (type:userstory AND targetRelease.KEY:1.0) OR (type:defect AND priority:highest).
Operators have no defined priority, so complex queries should be surrounded by parentheses. However queries like QUERY1 OR NOT QUERY2 are problematic and must be written in the form QUERY1 OR (NOT QUERY2). Queries, including sub-queries, can begin with the NOT operator: NOT severity:blocker, and severity:blocker AND (NOT priority:low OR HAS_VALUE:assignee.id) are valid queries. For example, something* is a valid query, but *something is not. Search terms cannot start with an asterisk (*). For example, to query for items with no value in the resolution field, use NOT HAS_VALUE:resolution. There is a special field HAS_VALUE, which can be used to determine whether or not an object has a value set in a field or not. White space can be also used to separate different values for one term.
White space has the same function as the OR operator, so the following queries are equivalent: severity:(blocker OR critical) OR priority:(highest OR high) will return the same result as severity:(blocker critical) priority:(highest high).
Operators must be typed in upper case: AND, OR, NOT. The following tips are relevant to Lucene queries specified in Polarion: The syntax is documented in the Apache Lucene Syntax Documentation, available on the Apache web site. Polarion's query language is essentially the same as that of Apache Lucene. This section is for advanced users who use command-line queries in the Query Builder, wiki macros, or the API.
0 kommentar(er)
