Investigation
An investigation of a specific build problem (/app/rest/investigations?locator=type:problem), a failed test (/app/rest/investigations?locator=type:test), or an entire build configuration (/app/rest/investigations?locator=type:anyProblem)
Related Help article: Working with Build and Test Failures
Properties
id
The investigation locator.
state
The investigation state. Supported values:
TAKEN — the investigation is assigned to a TeamCity user who works on resolving the problem.
FIXED — the investigation was marked as fixed.
GIVEN_UP — the investigation is no longer active, the 'no investigation' option was selected.
NONE — unknown investigation status.
href
The short (without the TeamCity server address) link to this investigation.
assignee
The TeamCity user assigned to this investigation.
assignment
Stores information about a user who assigned this investigation to the assignee, and the time of this event.
scope
A ProblemScope object that specifies the problem scope: individual build configuration, multiple configurations, or the entire project.
target
Stores the list of build problems and failed tests that are being investigated. If this is a configuration-wide investigation that does not target any specific issue, the ProblemTarget has empty tests and problems properties and its anyProblem returns true.
resolution
Specifies whether or not this investigation is resolved, and the current resolution policy.
responsible
This property is deprecated, use assignee instead.
Schema
Below, you can find a full schema of this object, in XML and JSON formats. You can choose what fields to submit depending on your current needs. Different methods might expect different fields: the best approach is to request this entity via GET and use the response as a base for the following POST request.
A link to another object implies that you can substitute it with the schema of the linked object, if it is required for your call.