Operations
Incident
Broken, lost or malfunctioning material, with its repair status.
Schemas: IncidentDto
Example
Generated from the schema
Broken, lost or malfunctioning material, with its repair status. An incident points to the item, serialized item, space, vehicle, order or project it affects, and blocksAvailability says whether it takes stock out of availability. It needs the incidence add-on: without it the answer is 402, not 403. The cost of the repair and the internal resolution note are not published.
Attributes
Unique incident identifier.
Human-readable incident number.
Short title of the incident.
Description; null if it has none.
Nature: damage, loss, malfunction, cosmetic, theft or custom.
What it affects: item, serializedItem, space, kit, vehicle or custom.
Available options: item, serializedItem, space, kit, vehicle, custom
Lifecycle status: draft, open, waiting, repairing, complete or lost.
Priority: urgent, high, medium, low or none.
Declared severity.
true when the incident removes the material from the available pool.
Affected units in bulk stock; null when not applicable.
Affected item; null if not applicable.
Affected physical unit; null if not applicable.
Affected space; null if not applicable.
Affected vehicle; null if not applicable.
Order in which it was detected; null if not applicable.
Associated project; null if not applicable.
Target resolution date in ISO 8601 UTC; null if it has none.
Comments the incident has.
Creation date in ISO 8601 UTC.
Last modification date in ISO 8601 UTC.
Values
- scope
item,serializedItem,space,kit,vehicle,custom
Returned by
GET /api/v1/incidents— List incidentsGET /api/v1/incidents/{incidentId}— Get an incident
Modified by
POST /api/v1/incidents— Open an incidentPATCH /api/v1/incidents/{incidentId}— Update an incidentPOST /api/v1/incidents/{incidentId}/comments— Comment on an incident
Was this page helpful?