support-issues

Report an in-app issue.

Files an in-app "Report an issue" submission against a dashboard (support-reporting epic). Open to any authenticated member wherever the surface exists — anyone hitting a dashboard problem must be able to report it, so this adds no per-user capability check beyond authentication. It IS edition-gated (POLISH-61): the deployment must have editionCapabilities.reportIssue true, which is false in snowflake mode, where a filed report would land in the app's own in-account Postgres and reach nobody at dvt — see the 403 below and the reportIssue cell on Me.editionCapabilities. The full dashboard spec is captured server-side from dashboardId (the client never sends the spec) and a best-effort render snapshot is attached. scope is element (with elementIds), page, or dashboard.

post/v1/support-issues

Request

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

Request body

dashboardIdstring uuid required

The dashboard the issue is about. The server reads its spec authoritatively — the client never sends the spec.

pageIdstring

The active page id, for context. Optional.

scope'element' | 'page' | 'dashboard' required

element flags specific panels (requires a non-empty elementIds); page flags the active page; dashboard flags the whole dashboard.

elementIdsstring[]

The flagged element ids. Required (non-empty) when scope is element; ignored otherwise.

bodystring required

The user's description of the problem.

Response

Support issue filed.

Changes

No recorded changes to this operation across all 1 revision of this API.