Add support tickets with private threads #18

2026-10-20T21:00:46Z

FernandoJVideira commented

2026-10-20 21:00:46 +00:00

Support tickets that run in private threads.

Panel with one button per category, each with its own staff role
Opening form (subject), one private thread per ticket
Claim and close (opener or staff), transcript sent to a log channel
/tickets setup|category|panel and /ticket add|remove|claim|close
Dashboard page to manage settings and categories and see open tickets

🤖 Generated with Claude Code

Support tickets that run in private threads. - Panel with one button per category, each with its own staff role - Opening form (subject), one private thread per ticket - Claim and close (opener or staff), transcript sent to a log channel - `/tickets setup|category|panel` and `/ticket add|remove|claim|close` - Dashboard page to manage settings and categories and see open tickets 🤖 Generated with [Claude Code](https://claude.com/claude-code)

FernandoJVideira added 1 commit 2026-10-20 21:00:46 +00:00

Add support tickets that work with private threads d294b3463b

Members open a ticket from a panel in the ticket channel: one button per
category (a dropdown past five), then a short form. Each ticket is a private
thread named after the category, number and opener, with a first message
that mentions the category's staff role so its members join, and Claim and
Close buttons.

- Claim: staff (the category's role, or Manage Threads / Manage Server)
  take a ticket; the first message shows who has it.
- Close: the opener or staff close it, with an optional reason. The thread
  is locked and archived, and the log channel gets a summary and a .txt
  transcript of the whole thread.
- /ticket add|remove|claim|close inside a ticket; /tickets setup,
  /tickets category add|remove|list and /tickets panel for admins.
- Per-member limit on open tickets (default 1), per-server ticket numbers
  handed out atomically, a deleted thread closes its ticket.
- The dashboard asks the bot to post or refresh the panel through
  ticket_commands (LISTEN/NOTIFY, like music); the listener reconnects if
  the database connection drops.
- Setup warns about missing bot permissions in the ticket and log channels.

The flows live in internal/tickets behind small Discord and store
interfaces, with unit tests on fakes; the repo and the listener have
integration tests (-tags integration, TICKETS_TEST_DB).

Needs the ticket tables (velox-dashboard-api migration 000016_tickets).
.gitignore gains the /tldr benchmark rules so private chat exports and
benchmark results on disk can't be committed from this branch.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

FernandoJVideira merged commit 95072fcd53 into dev

2026-10-20 21:03:04 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FernandoJVideira/velox-bot#18