YouTrack Issue & Bug Tracker

Some important news today.

First, you can now follow us on twitter for quick development updates.

Second, YouTrack FAQ has been published in response to feedback that we have received this month. Particularly, it explains:

• How to create new users when they don’t create themselves.
• What’s wrong (or not) with YouTrack when you’re unable to assign an issue to yourself.
• How to simulate subtasks in YouTrack with issue linking.
• Whether it’s possible to visually distinguish between different types of issues.
• Whether YouTrack integrates with version control systems.

That’s not all FAQ is about: see if there are answers to questions you’ve been afraid to ask. If not, ask on, and we’ll answer!

As you’ve probably noticed, we’re reducing the amount of notifications by merging changes made by one user into a single e-mail containing only the resulting change. That enables fast tweaking of reported issue without bothering its assignee several times.

Moreover, if your e-mail client supports threading, notifications about the same issue can be merged into a single thread.

GMail conversations are supported too:

And that’s how it looks in Thunderbird:

Enjoy!

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:

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:
  

  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:
  

  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 (#):
  

  #unresolved

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).

Consider you have to create a link from one issue to another. You select “Link->Relates to” from menu, or type “relates to” and get the following dialog:

At this moment it appears that you do not remember target issue number. What to do? Use text search right here:

Navigate to desired issue and press Tab:

Bingo.

And then it is shown near your comments.

Charisma now supports color tags. Select tag color in edit dialog:

And view colored tags in issues list:

Now you can do it in search field:

… and in commands popup:

Also, your recent searches and recent commands are suggested as well now:

Fix bugs with pleasure