TeamCity Cloud 2023.09 Help

Investigations Auto Assigner

TeamCity can analyze build problems (for example, compilation errors) and test failures, and try to identify users whose commits potentially led to these problems.

For failed tests, TeamCity suggests these potentially responsible users as investigators.

Automatic Investigation Suggestions

In addition to suggestions, you can now add the Investigations Auto Assigner build feature that uses the same heuristics to assign investigations of failed tests and build problems automatically. A user assigned as an investigator will see the corresponding notification next to the Administration button.

Investigation automatically assigned to a user

Feature Settings

The Investigations Auto Assigner feature is functional out of the box. All of its settings are optional.

AutoAssigner Feature Settings

Setting Name



Allows you to ignore the first occurrences of build issues and automatically assign investigators only for repeatedly occurring problems. See this section for more information: Delay Automatic Assignment.

Default assignee

The Investigations Auto Assigner attempts to identify the following users who are potentially responsible for a failure:

  • A user who was the only committer to the build.

  • A user who was the only committer to the suspicious file. A suspicious file is the one whose name appears in the test or build problem error text.

  • A user who was previously responsible for this problem.

If no such user was found, the investigation will be assigned to the default assignee.

Users to ignore

The list of users who should never be automatically appointed as investigators, even if they satisfy the aforementioned conditions.

Build problems to ignore

Choose the types of problems that do not require investigators to be assigned automatically.

Delay Automatic Assignment

If necessary, you can delay the auto-assignment of investigations.
TeamCity needs time after the build finish to detect flaky tests. In some cases, Investigations Auto Assigner may assign an investigation to a user even if the build fails without any user involvement. When there are many flaky tests in a project, this may be distracting.

To prevent this scenario, select Assign: "On second failure" when configuring this build feature. Investigations Auto Assigner will delay the assignment until the problem repeats in a build configuration twice in a row (in the default branch). This option affects only failed tests and "Exit code" build problems; any compilation errors will be assigned with an investigation right on the first failure.

Last modified: 03 April 2023