API: tickets
Это содержимое пока не доступно на вашем языке.
GET /api/v1/tickets
Section titled “GET /api/v1/tickets”List Board
The owner board — defects/incidents by default, or a vote-ranked suggestion
backlog with ?kind=suggestion (SPEC-004 §3.9). Team-readable (owner + team,
SPEC-112 §3.3) — the defect section of the tasks board; agents still get 403.
| Parameter | In | Required | Type |
|---|---|---|---|
kind | query | no | object |
status | query | no | object |
component | query | no | object |
area | query | no | object |
severity | query | no | object |
since | query | no | object |
limit | query | no | integer |
POST /api/v1/tickets
Section titled “POST /api/v1/tickets”File Ticket
Intake one report; return a bare 202 (SPEC-004 §1.5 / §3.3).
Write-only fire-and-forget: no ticket id, no dedup verdict — a hostile or looping reporter gets nothing back to react to. Over the flood cap → 429; an oversized body → 413.
PATCH /api/v1/tickets/{guid}
Section titled “PATCH /api/v1/tickets/{guid}”Transition Ticket
Resolve / dismiss / promote a ticket, state-machine-guarded (SPEC-004 §3.5).
Owner-only. An illegal transition (e.g. closing an already-closed ticket) → 409.
| Parameter | In | Required | Type |
|---|---|---|---|
guid | path | yes | integer |