1 Ticket Commands EN
darksoon edited this page 2026-05-13 21:28:31 +02:00

Ticket Commands

Two command sets:

  • /tickets — Administration (panels, history, force-close, reopen, settings)
  • /ticket — In-ticket actions (close, claim, info, transfer)

/tickets — Administration

Command Permission Function
/tickets setup-panel <panel-id> Manage Guild Manually (re-)post a panel — handled automatically on bot start
/tickets list-panels Manage Guild Show all configured panels with their status
/tickets history <user> Manage Guild All tickets for a user (🟢 open / closed)
/tickets force-close <id> [reason] Manage Guild Close a ticket from outside (even if the channel is gone)
/tickets reopen <id> Manage Guild Re-open a closed ticket — channel is recreated
/tickets set-channel <feature> <channel> Manage Guild Set the log or transcript channel
/tickets show Manage Guild Embed overview of all ticket settings
/tickets reload Manage Guild Reload tickets.yml

/ticket — In-Ticket Actions

Command Permission Function
/ticket close [reason] Owner or category staff Close the current ticket (transcript + rating)
/ticket claim Category staff Claim the ticket
/ticket unclaim Category staff Release the ticket
/ticket info Anyone in the ticket Owner, category, status, claim, open date, form responses
/ticket transfer <category-id> Category staff Move the ticket to another category in the same panel

Category staff = users with a role listed in staffRoleIds for the respective category.


In-Ticket Buttons

Button Who Function
Claim / Unclaim Category staff (when claimable: true) Toggle claim
Close Owner or category staff Modal for optional reason → close flow

The close button checks the permission — nobody except the owner and category staff can close the ticket.


Auto-Deployment

On bot start all enabled panels are automatically posted to their channel (tracked via the TicketPanelMessage database table). If a panel message is manually deleted, the bot posts a new one on the next start. The commands are only needed for manual re-deploy and channel changes.


Examples

/tickets force-close 42 reason: "Resolved via DM"
/tickets reopen 42
/ticket transfer category-id: report
/tickets history user: @Jonas

→ More details in GrumpyTickets-EN