Incidents
Count incidents by status
Returns how many incidents there are in each status, with optional filters by project, space, vehicle, item, physical unit or order.
incidents:readincidents:read- 120/min
- May need an add-on
- Server annotation: Read-only
- Server annotation: Idempotent
Result
generated from the schema
The six keys always come out, with 0 if there are none. It is the only way to discover the volume: this resource does not publish a listing.
Arguments
Filter by project.
Limits: min length 1, max length 100
Filter by space.
Limits: min length 1, max length 100
Filter by vehicle.
Limits: min length 1, max length 100
Filter by catalog item.
Limits: min length 1, max length 100
Filter by physical unit.
Limits: min length 1, max length 100
Filter by order.
Limits: min length 1, max length 100
Result
On success the result carries structuredContent with data and meta. These are the attributes of data.
Show the attributes of data
Incidents in draft.
Open incidents.
Waiting incidents.
Incidents under repair.
Resolved incidents.
Material declared lost.
An error is a result with isError: true and the problem in content[0].; there is no structuredContent. See Errors.
The same operation by REST
This tool runs GET /api/v1/incidents/status-counts.
Related pages
Link to this section: Related pagesIncidents
Count incidents by status
Returns how many incidents there are in each status, with optional filters by project, space, vehicle, item, physical unit or order.
Guides
Safe writes
An assistant that can write can also write the wrong thing. Decide which tools need a person, retry without duplicating, and know what a write sets in motion.
Guides
Errors
A tool error is a result with
isError: trueand the problem in the first text block. Branch on itscode.
Was this page helpful?