Issues

Update an issue

Changed on

Change an issue's severity, with an optional note recorded in its history. A change notifies no one.

patch/issues/{issueId}

Request

  • Base URL: https://api.sazabi.com/v1
  • URL: https://api.sazabi.com/v1/issues/{issueId}
  • Auth: none declared

Path parameters

issueIdstring uuid required

Issue ID to update.

Request body

severity'low' | 'medium' | 'high' | 'critical' required

Issue severity, by impact. critical: Happening now in production: an outage of the service, of a flow most users depend on, or of a whole feature; or data loss, a security exposure, or failed payments. high: Happening now in production: at least 1% of attempts failing or a region down; or production data loss, exposure, or failed payments that has stopped. medium: A failure limited to a few users or one path, a broad internal failure, a production outage that ended on its own, or serious harm outside production. low: No user or system impact, a transient blip, an internal failure on one item or a rare path, or other work outside production, including eval, training, and canary runs. A change notifies no one: it updates the issue, its status-page incident, and its Slack cards.

notestring

Optional context for the severity change, up to 500 characters. Shown in the issue's history. State the observed reason in brief, natural language without emojis or em dashes; distinguish confirmed impact from uncertainty.

Response

OK

changedboolean required

False when the issue already had the requested severity.

Changes