Tickets list and reply workflow

Filter tickets (new/open/closed). Reply on /tickets/{id}. Bulk close supported; closed tickets reject replies.

Tickets list and reply workflow

Staff queue for member support tickets.

Where to find it

Admin → TicketsTickets list (/admin/tickets)

How it works

Filter by Search, Category, Status (New / Open / Closed). Default 30/page. View opens the member thread at /tickets/{id} (admin /admin/tickets/[id] redirects there). Opening as staff marks staff-read.

Reply body 20–8000 chars; optional one attachment ≤10 MB. Any reply on a new ticket moves it to open. Closed tickets reject replies until reopened. Bulk Close selected (max 200 IDs) keeps the thread readable. Single ticket delete exists via API; assignee is API-only (not in the list UI).

Sidebar: red = new count; blue = unread owner replies on non-new tickets.

Common problems

Looking for an admin-only reply screen

Replies happen on /tickets/... with a back link to the list.

Staff cannot reply

Ticket is Closed - set it back to Open first.

Related