New EAP build, new search syntax
August 18th, 2009 by Jura GorohovskyWe’ve published a new EAP build which introduces a couple of major syntactic changes in the way you search for issues. We’ve made the transition with two goals in mind:
- To streamline full-text search.
- To provide a way to clearly separate attributes and values from other query items.
Here’s a simple query to summarize the modified syntax:
for: {Maxim Mazin} #unresolvedThe following list describes the changes in more detail:
- Colon after attributes. When you specify an attribute (
for,state,priorityetc.), it should be followed by a colon:
state:If you use query completion, the colon is inserted automatically.
- Curly braces around attribute values that contain spaces. When you specify an attribute value that contains more than a single word, use curly braces (
{}) to surround it:
Again, the braces are added automatically when you choose attribute values using query completion.
- # as prefix for values without attributes. When you specify an attribute value without the corresponding attribute, it should be preceded by the hash mark (
#):
In addition, we’ve extended your search toolset to include the following features:
- “-” operator is introduced to subtract a subset from a set of search query results. For example,
displays all unresolved issues excluding those with critical priority. Note that you shouldn’t put the hash mark before a lonely attribute value when you use the “-” operator, as in the example above.
- Sort order for “sort by”. Using the new
ascanddesckeywords, you can now specify whether to sort the list of found issues in ascending or descending order:
See the list of other implemented features and fixed bugs, and download the latest EAP build (#54).
October 6th, 2009 at 9:27 am
[...] is to search for it using our search box. However, if you don’t feel comfortable with our search syntax, you can use filters to the left of the list of [...]