New EAP build, new search syntax

#query_div .query_link:link, .query_link:hover, .query_link:visited {text-decoration:none; color:black; border-bottom:0px;}

We’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} #unresolved

The following list describes the changes in more detail:

  • Colon after attributes. When you specify an attribute (for, state, priority etc.), it should be followed by a colon:


    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:

    in: {JetBrains Tracker}

    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,

    #unresolved -critical

    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 asc and desc keywords, you can now specify whether to sort the list of found issues in ascending or descending order:

    priority: critical sort by: updated asc

See the list of other implemented features and fixed bugs, and download the latest EAP build (#54).

image description