Ticketing System by a-Digi-a · Pull Request #120 · redbrick/blockbot

a-Digi-a · 2026-06-14T18:50:56Z

A ticketing system where people can contact either helpdesk, admins or the entire committee privately through the Redbrick discord instead of DM's.

How it works:

A channel will be made for tickets (under the technical category)
One of the admins will need to run /create_ticket_message [new channel name]
A message will be sent by blockbot in the new channel, users can then click a button on this message
On clicking the button, users will be prompted to choose which category of committee they want to contact and fill in their reason for the ticket
A channel will be created with the name ticket-user-[number]
This channel will have a message by blockbot where users can click a button to close the ticket when solved, deleting the channel and it will ping the user/committee added

novanai · 2026-06-15T18:41:05Z

+    ctx: BlockbotContext,
+    channel_option: arc.Option[
+        hikari.TextableChannel,
+        arc.ChannelParams("A textable channel option.", name="channel"),


Could use a better option description

Oops forgot to change the boilerplate code :P

novanai · 2026-06-15T18:43:18Z

+    channel_option: arc.Option[
+        hikari.TextableChannel,
+        arc.ChannelParams("A textable channel option.", name="channel"),


I think if you call the parameter channel (instead of channel_option) you don't have to specify name="channel" ... I think...

Ill check it out

novanai · 2026-06-15T18:44:30Z

+        arc.ChannelParams("A textable channel option.", name="channel"),
+    ],
+) -> None:
+    embed = hikari.Embed(title="Tickets", description="Create a ticket here!")


Could describe what you might open a ticket for

Any suggestions on what to write? I feel like I'd just make it kind of long winded explaining it.

Something like "Need to contact admins, helpdesk, or the whole committee? Open a ticket!" maybe?

novanai · 2026-06-15T18:47:15Z

+@plugin.listen()
+async def button_click(event: hikari.InteractionCreateEvent) -> None:
+    if not isinstance(event.interaction, hikari.ComponentInteraction):
+        return
+    if event.interaction.custom_id != "meowmeow1":
+        return


You could use a single event listener which filters events and calls functions instead

e.g.

# one listener @plugin.listen() async def on_interaction(event: hikari.InteractionCreateEvent) -> None: if isinstance(event, ComponentInteraction) and event.custom_id == "meowmeow1": await handle_meowmeow1(event) # repeat for all existing listeners async def handle_meowmeow1(event: ComponentInteraction): # this could be ModalInteraction, etc ...

Good point, I'll refactor it

novanai · 2026-06-15T18:48:09Z

+    for value in ("admins", "helpdesk", "committee"):
+        committee_select.add_option(value.title(), value)
+    committee_label = se.LabelComponentBuilder(
+        label="Committee", component=committee_select


Is it possible to add a description here? e.g. "Who do you wish to contact"

May have forgot to do that...

novanai · 2026-06-15T18:49:26Z

+    existing_names = {
+        channel.name
+        for channel in channels
+        if hasattr(channel, "parent_id")


I'd rather you check it's an instance of a category channel (not sure what the classname is) instead of checking for an attribute

I tried searching for a way to search through the channels in the category but couldn't find them

oh I meant something like

isinstance(channel, hikari.GuildCategory)

instead of the hasattr check

ah i see, makes sense

novanai · 2026-06-15T18:52:42Z

+        flags=hikari.MessageFlag.EPHEMERAL,
+    )
+    await event.app.rest.create_message(
+        created_channel.id, f"<@&{permission_role}> <@{event.interaction.user.id}>"


You can just pass create_channel here. Although I'd rather you include this in the original message as the content. Also, to make it actually ping the role + user, you'll have to set the user_mentions and role_mentions parameters to True

You can just pass create_channel here

Idk what you mean tbh.

Although I'd rather you include this in the original message as the content.

The original message (I assume you mean the one above it) is sent in the channel for creating tickets just for that user, the new one pings the user and role for who they want to contact.

Also, to make it actually ping the role + user, you'll have to set the user_mentions and role_mentions parameters to True

Thanks I'll make sure to set those parameters.

Idk what you mean tbh.

create_channel instead of create_channel.id

original message

oh I meant the one with the embed send in the new channel sorry
e.g. create_message(content="<pings>", embed=embed, ...)

novanai · 2026-06-15T18:53:38Z

+        hikari.ResponseType.MESSAGE_CREATE,
+        "Closing ticket...",
+        flags=hikari.MessageFlag.EPHEMERAL,
+    )


Might want to sleep for a few seconds here (asyncio.sleep) so the user can actually see the message before the channel is deleted

Good point, ill make it sleep for like 3 seconds

Arisamiga · 2026-06-15T18:57:09Z

+CATEGORY_IDS: dict[str, int] = {
+    "official": 568810044309766151,
+    "administration": 568810044309766151,
+    "technical": 1202325296133701723,
+    "general": 627868752310042627,
+    "general-bots": 1202319516407697438,
+    "webgroup": 1202321207811395624,
+    "voice-channels": 568403964098248723,
+    "archive": 958448000496173056,
+}


The only category we use is technical; there is no need to include the other categories.

Its mainly for future use too, there's other dictionaries for things like roles in that file I thought I might as well complete it

Its mainly for future use too, there's other dictionaries for things like roles in that file I thought I might as well complete it

Okay, but make sure that the correct IDs are used instead of placeholder ones. It would also be helpful if the dictionary keys matched the category names. But it would be good to keep the config file free of unnecessary parameters.

Arisamiga · 2026-06-15T19:31:37Z

+async def delete_channel(event: hikari.InteractionCreateEvent) -> None:
+    if not isinstance(event.interaction, hikari.ComponentInteraction):
+        return
+    if event.interaction.custom_id != "moomoo1":


This is quite nice and funny naming, but it would be good to also have some context on the IDs used. Maybe something like moomoo-del might be better

Good idea :P

initial commit

64444c3

a-Digi-a self-assigned this Jun 14, 2026

a-Digi-a added this to Webgroup Jun 14, 2026

a-Digi-a added the enhancement New feature or request label Jun 14, 2026

github-project-automation Bot moved this to 📋 Backlog in Webgroup Jun 14, 2026

a-Digi-a linked an issue Jun 14, 2026 that may be closed by this pull request

Add ticketing system #119

Open

a-Digi-a marked this pull request as draft June 14, 2026 18:51

complete ticketing system

3e644c0

a-Digi-a marked this pull request as ready for review June 15, 2026 15:49

fix .env.sample

636ab73

a-Digi-a requested review from Arisamiga, CG-5228 and novanai June 15, 2026 15:52

a-Digi-a added 5 commits June 15, 2026 16:53

fix formatting

9f17a6f

add git to dockerfile

0ff7ed8

make ticketing command admin-only

6fc5f33

fix formatting (again)

bff2424

use hook for command permission

ef82f5c

novanai requested changes Jun 15, 2026

View reviewed changes

github-project-automation Bot moved this from 📋 Backlog to 🖐 Assigned in Webgroup Jun 15, 2026

Arisamiga requested changes Jun 15, 2026

View reviewed changes

Conversation

a-Digi-a commented Jun 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

a-Digi-a commented Jun 14, 2026 •

edited

Loading