Bug Reports Module
Structured bug tracking with severity tags, me-too votes, staff workflow buttons, and optional threads.
Overview
Members post bugs in a dedicated channel. Lio removes the original message and posts a numbered embed with severity, status, and action buttons.
Others can click Me too to vote. Staff move bugs through confirm → in progress → resolved or won't fix.
Optional discussion thread per bug and DM to the author when their report is posted.
Setup
- Enable Bug Reports in Modules.
- Set Bug report channel and staff roles who may update status.
- Optional: discussion threads, ping staff on [critical], DM on post.
- Save — new messages in the channel become bug embeds.
Severity tags
Start your message with [critical], [high], [medium], or [low] to set severity. Without a prefix, medium is used.
Example: [critical] Dashboard save button does nothing on mobile
- critical — red highlight; can ping staff roles when enabled.
- high / medium / low — color-coded on the embed.
- Status buttons update the embed and archive the thread when closed.
Key settings
- Bug report channel — plain messages here become bug embeds.
- Staff roles — can use Confirm, In progress, Resolve, Won't fix.
- Discussion threads — optional thread under each bug.
- Ping staff on critical — mentions staff roles for [critical] reports.
- Send DM — off by default; notifies author when the embed is posted.
Usage
- Post a text message (with optional severity prefix) in the bug channel.
- Members click Me too to add their vote.
- Staff use workflow buttons on the embed; resolved and won't fix lock the report.
Troubleshooting
- Message not converted → module off? wrong channel?
- Cannot update status → user needs a staff role or Manage Server.
- No thread → enable discussion threads in config.
- Critical ping missing → enable Ping staff on critical and set staff roles.