Listing and detail
GET /api/tickets
GET /api/tickets/:id
GET /api/tickets/board (developer)
GET /api/tickets/workload
Stats and feeds
GET /api/tickets/stats/overview
GET /api/tickets/stats/activation (developer)
GET /api/tickets/stats/usage (developer)
GET /api/tickets/closure-summaries/index-feed (developer)
Write operations
POST /api/tickets (multipart, attachments)
PATCH /api/tickets/:id
POST /api/tickets/:id/comments
POST /api/tickets/:id/attachments
GET /api/tickets/:id/related
POST /api/tickets/:id/related (developer)
DELETE /api/tickets/:id/related/:relatedId (developer)
External references
GET /api/tickets/:id/external-references
POST /api/tickets/:id/external-references (developer)
DELETE /api/tickets/:id/external-references/:refId (developer)
Important business rules
- Users can update ticket only while status is
submitted (ticket_locked otherwise).
- Closing transition requires closure summary comment (
closure_summary_required).
- Create ticket validation is stricter for
bug and for feature/improvement content length.