Remove the one-ticket-at-a-time limit #1091

Open
opened 2026-08-20 05:04:55 +00:00 by coilyco-ops · 0 comments
Member

Filed from the Sirens Discord #suggestions-feedback-bugs forum.

Source // https://discord.com/channels/1300204416229441587/1532876024717643966
Raised by // Kai, 2026-07-31
Forum tags // discord meta
Signal // no replies, 1 thumbs up

Routing note // One of three discord meta threads with no home in the eco repos. Kai routed them here on 2026-08-20.

What was asked

Drop the restriction that a member may only have one open ticket at a time.

The thread body is //, so the title is the whole suggestion.

Context

#tickets is opened with /new <some words>, which creates a per-ticket channel. Its topic states that admins do not see the ticket description, only the channel that follows. The channel also carries a 30 second slowmode.

The limit forces a member sitting on two unrelated problems to serialize them, or to fold both into one channel where they get tangled.

What to check before removing it

  1. Whether the limit is a setting on the ticket bot or something enforced by hand.
  2. Whether it exists as spam protection. If so, the slowmode and a higher cap may cover the same ground without the serialization cost.
  3. Whether anything downstream assumes one open ticket per member, such as transcript handling in #admin-transcripts.

Given the thread has no discussion at all, the original reason for the limit is not recorded anywhere reachable. Worth asking Kai before removing rather than assuming it was arbitrary.

Filed from the Sirens Discord `#suggestions-feedback-bugs` forum. **Source** // https://discord.com/channels/1300204416229441587/1532876024717643966 **Raised by** // Kai, 2026-07-31 **Forum tags** // discord meta **Signal** // no replies, 1 thumbs up **Routing note** // One of three `discord meta` threads with no home in the eco repos. Kai routed them here on 2026-08-20. ## What was asked Drop the restriction that a member may only have one open ticket at a time. The thread body is `//`, so the title is the whole suggestion. ## Context `#tickets` is opened with `/new <some words>`, which creates a per-ticket channel. Its topic states that admins do not see the ticket description, only the channel that follows. The channel also carries a 30 second slowmode. The limit forces a member sitting on two unrelated problems to serialize them, or to fold both into one channel where they get tangled. ## What to check before removing it 1. Whether the limit is a setting on the ticket bot or something enforced by hand. 2. Whether it exists as spam protection. If so, the slowmode and a higher cap may cover the same ground without the serialization cost. 3. Whether anything downstream assumes one open ticket per member, such as transcript handling in `#admin-transcripts`. Given the thread has no discussion at all, the original reason for the limit is not recorded anywhere reachable. Worth asking Kai before removing rather than assuming it was arbitrary.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo#1091
No description provided.