Issue Reporting

Issue Reporting lets members submit bug reports and feature requests from Discord, then routes approved reports to GitHub.

Scope

• Submission is Discord client-only through slash commands.
• There is no dashboard module for Issues.
• Reviews are handled in a private Discord review channel.
• Approve/reject actions are currently restricted to the configured bot owner account.

Command Surface

• /issue bug
• /issue feature
• /issue notify (bot owner only, see Close Notifications)

/issue bug and /issue feature open a modal to collect details.

Workflow

1. A member submits /issue bug or /issue feature.
2. The report is saved with pending status.
3. A review message is posted in the configured review channel.
4. Authorized reviewer clicks Approve or Reject.
5. Approved reports create GitHub issues with category labels.
6. User is notified by DM when possible.

Close Notifications

When an approved report's GitHub issue is closed, the reporter gets a direct message saying so (nothing happens if their DMs are closed). The bot checks for closed issues every hour.

/issue notify runs that check immediately instead of waiting for the next hourly pass. It is owner-only (the configured bot owner account); other users are told it is owner-only, and it replies privately with how many reporters were notified, how many had DMs closed, and how many failed. Members never need it.

Safeguards and Limits

• Submissions are rate-limited per user to prevent abuse.
• Title and content are validated/sanitized before storage.
• Pending review views are restored automatically after bot restarts.

Operational Requirements

The issue reporter cog only loads when both are configured:

• GITHUB_PAT
• GITHUB_REVIEW_CHANNEL_ID

If either is missing, issue commands are not registered.