---
title: "Update triage state on a support issue."
method: PATCH
path: "/v1/support-issues/{id}"
tags: ["support-issues"]
---

# Update triage state on a support issue.

`PATCH /v1/support-issues/{id}`

## Request

- Base URL: `http://localhost:8080`
- URL: `http://localhost:8080/v1/support-issues/{id}`
- Auth: one of:
  - API key in cookie `dvt_session`
  - HTTP bearer

The triage write-back (used by the triage workflow): set the `status` and optionally the filed `triageTicket` and classification `triageNotes`. Admin surface — requires `support_issue:manage`.

## Request body

- PatchSupportIssueRequest: The triage write-back. Set `status`; optionally set/clear `triageTicket` and `triageNotes`.
  - `status` 'open' | 'triaging' | 'ticketed' | 'resolved' | 'dismissed', required: The new triage status.
  - `triageTicket` string: The filed PM ticket friendly-id. Omit to leave unchanged; send "" to clear.
  - `triageNotes` string: The classification / suggested-fix note. Omit to leave unchanged; send "" to clear.

## Response `200`

Support issue updated.

- SupportIssueEnvelope
  - `data` SupportIssue, required: An in-app "Report an issue" submission (support-reporting epic): a user's description of a dashboard problem, scoped to the whole dashboard, the active page, or specific elements, with the full dashboard spec captured at submit time and a best-effort render snapshot. Org-scoped and tenant-isolated (ADR-0025). `specSnapshot` is present on the single-issue GET and omitted from the list.
    - `id` string, uuid, required
    - `orgId` string, uuid: The org the issue was filed in. Present on the triage (admin) reads; omitted from the submitter's create response.
    - `submittedBy` string, uuid, required: The user who filed the issue.
    - `dashboardId` string, uuid, nullable: The reported dashboard. Null if the dashboard was later deleted (the spec snapshot is the durable record).
    - `pageId` string, nullable: The active page id at submit time. Null/omitted for a whole-dashboard report.
    - `scope` 'element' | 'page' | 'dashboard', required: What the report targets. `element` carries `elementIds`; `page`/`dashboard` carry none.
    - `elementIds` string[], required: The flagged panel/element ids (empty for page/dashboard scope).
    - `body` string, required: The user's free-text description.
    - `specSnapshot` object: The full dashboard spec at submit time. Present on GET by id; omitted from the list.
    - `renderId` string, uuid, nullable: Reserved for a render snapshot of the dashboard at submit time. Always null for now — snapshot capture with a dedicated render budget is a follow-up; the triage agent re-renders from `specSnapshot` on demand in the meantime.
    - `status` 'open' | 'triaging' | 'ticketed' | 'resolved' | 'dismissed', required: Triage lifecycle state. Submissions start `open`.
    - `triageTicket` string, nullable: The PM ticket friendly-id filed for this issue during triage (e.g. "DVT-1234").
    - `triageNotes` string, nullable: The triage agent's classification / suggested-fix note.
    - `createdAt` string, date-time, required
    - `updatedAt` string, date-time, required
  - `meta` Meta, required: Response metadata.
    - `requestId` string, required: Correlates with the X-Request-Id header.
    - `total` integer: Item count, present on collection responses.
    - `nextCursor` string, nullable: Opaque keyset-pagination cursor, present on paginated responses (e.g. GET /v1/dashboards) when more rows exist beyond this page. Pass it back as the `cursor` query param to fetch the next page; absent or null on the last page.
    - `roleResolveDegraded` boolean: Snowflake mode only (DVT-2260), on GET /v1/dashboards: present and true when the caller's live Snowflake role resolution failed or was unavailable — role-shared dashboards may be missing from this page. Omitted (not merely false) whenever resolution succeeded or the role-share arm does not apply (off snowflake mode, an org admin/owner, or off the ingress listener).

## Other responses

- `400`: Malformed request.
- `401`: Missing, invalid, or expired session.
- `403`: The caller's role does not permit this action.
- `404`: Resource does not exist.

---

[API](https://skmtc.dev/dvt/apis/dvt-rest-api.md) · [All operations](https://skmtc.dev/dvt/apis/dvt-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dvt/apis/dvt-rest-api/revisions/00016f504165?raw)