After you have installed and started running TeamCity, it collects the information on builds, tests and so on and indexes it.
In TeamCity you can search builds by build number, tag, build configuration name and other different parameters specifying one or several keywords and use Lucene search query syntax to get more precise results.

For complete list of available search fields (keywords) please refer to Complete List of Available Search Fields section.

In this section:

Search Query

In TeamCity you can search for builds using the Lucene query syntax. Though in TeamCity search query has two major differences, please refer to the Lucene documentation for complete syntax rules description.
To narrow your search and get more precise results you can use available search fields - indexed parameters of each build. Please refer to the Complete list of available search fields for more details.

Differences from Lucene Syntax

When using search query in TeamCity, please pay attention to the following major differences in query syntax from Lucene native syntax:

  1. By default, TeamCity uses AND operator in query. That is, if you type in the following query: "failed @agent123", then you will get a list of all builds that have keyword "failed" in any of its search fields, and were run on build agent, which name is "agent123".
  2. By default, TeamCity uses "prefix search", not exact matching like Lucene. For example, if you search for "c:main", TeamCity will find all builds of the build configuration which name starts with "main" string.
    {tip}Prefix search is not used for query with search keywords. In this case you can use wildcards ("\*" and "?"). For example, a query "tests:FxCopFile*" will results in list of all builds that include tests which names start with "FxCopFile".{tip}

Performing Fuzzy Search

You also have a possibility to perform fuzzy search using the tilde, "~", symbol at the end of a single word term which to search items similar in spelling.

Boolean Operators and Wildcards Support

You can combine multiple terms with Boolean operators to create more complex search queries. In TeamCity, you can use AND, "+", OR, NOT and "-".

When using Boolean operators, type them ALL CAPS.

TeamCity also supports usage of "*" and "?" wildcards in the build query.

Please do not type an asterisk sign, *, at the beginning of the search term because it can take a significant amount of time for TeamCity to search its database. For example, *onfiguration search term is incorrect.

Complete List of Available Search Fields, Shortcuts, and Keywords

Search Fields

When using search keywords, use the following query syntax:

<search field name>:<value to search>

Search Field






Find all builds that were run on specific agent.

agent:unit-77, or agent:agent14*



Find all builds that include changes with specific string.

build:254 or build:failed



Find all builds that include changes with specific string.

changes:(fix test)



Find all build that include changes committed by specific developer.




Find all builds from the specific build configuration.

c:(Nightly Build)



Find all builds that contain a file with specific revision.




Find all build that include files with specific filename.




Find all builds that include changes with specific VCS label.




Find all builds that were pinned and have specific word (string) in the pin comment.




Find builds from specific project.




Find all builds that include changes with specific revision (e.g., you can search for builds with specific changelist from Perforce, or revision number in Subversion, etc.).




Find all builds that started at the specific time (search by timestamp).




Find all builds with specific status.




Find all builds with specific tag.




Find all builds that include specific tests.




Find all builds that were triggered by specific user.




Find builds that have specific VCS.



In addition to above mentioned search fields, you can use two following shortcuts in your query:

Please pay attention that when you use these shortcuts, you should not insert colon after it. That is, the query syntax is as follows: <shortcut><value to search>





Search for build number.

#<number>, e.g. #1234


Find all builds that were run on the specific agent.

@<agent's name>, e.g. @buildAgent1

Using Double-Colon

You can use double-colon sign (::) to search for project and/or build configuration by name:

"Magic" Keywords

TeamCity also provides "magic" keywords (for the list see table below). These magic keywords are formed of the '$' sign and a word itself. The word can be shortened up to the one (first) syllable, that is, the $labeled, $l, and $lab keywords will be equal in query. For example, to search for pinned builds of the "Nightly build" configuration in the "Mega" project you can type any of the following queries:

Magic word



Search for builds with tags. For example, Calcutta::Master $t query will result in a list of all builds marked with any tag of build configurations which name is started with "Master" from projects with names started with "Calcutta".


Search for pinned builds.


Search for builds that have been labeled in VCS. For example, to find labeled builds of the Main project you can use following queries: p:Main $labeled, or project:Mai $l, or m:: $lab, etc.


Search for builds that have been commented.


Search for personal builds. For example, using -$p expression in your query will exclude all personal builds from search results.

h2. Performing Search 
*To find the desired issues:*

# Navigate to the search field located in the upper-right corner of TeamCity web UI. \\
# Type the search criteria and press the *Enter* or *Return* key.
By default, TeamCity will search all builds-related data such as project and build configuration name, changes committer name, vcs root, trigger, changes description and so on. The results appear in a new pop-up window:\\
{note}By default, TeamCity searches for all items you type in the search field.
# Click the *view results on a separate page* link to explore the search details. On the page that opens you can view the results summary:
{note}You will see only search results from projects you have [permission | Role and Permission] to view. 

In the example above the keywords were found in developer's changes, project, build status and build trigger. 

{tip}By default, search results on the dedicated search results page (not in pop-up) are sorted by relevance. You can also sort results by time. To do so, select proper item in a drop-down list to the right of the search query field.