Compare /12 min read
Best Discord Bots for Bug Reports and Suggestions
Suggestion bots, bug-report bots and Discord's own forums, compared for game communities: votes, duplicates, statuses, and what each costs.
Many lists of Discord feedback bots are out of date. They still recommend Suggester, which shut down on July 19, 2025 while its top.gg page kept showing tens of thousands of servers. This one was checked tool by tool in October 2026.
It’s written for game communities, where the people posting are players, the same bug arrives forty times after a patch, and someone has to tell them when it’s fixed. BetaHub is one of the tools below; we say where it’s the wrong pick.
The short answer
- You want a suggestion box with votes, free: Suggestions. If Carl-bot is already in your server, its suggestions module does the same job.
- You want bug reports turned into GitHub issues: Submitty, on its premium plan. The sync is one-way.
- Your team already plans in Codecks: its own bot, Decky.
- You want nothing to install: Discord’s Forum channels with required tags.
- You need bugs and suggestions from players in one place, with duplicates merged, screenshots and logs attached, statuses sent back to players, and issues pushed to Jira or GitHub on a paid plan: BetaHub.
What a game community needs from a feedback bot
A suggestion box for a hobby server and a bug pipeline for a live game are different jobs. Five questions separate them:
- Can players submit without leaving Discord? Anything that sends them to a web form loses reports.
- What happens to duplicates? After a patch the same crash is reported dozens of times. Either a person merges them by hand, or the tool does.
- Do reporters hear back? Players who never learn what happened to their report stop reporting.
- Can a report carry evidence? Screenshots, video and log files decide whether a bug can be reproduced.
- Does it reach your tracker? If the team works in Jira or GitHub, a report that stays in Discord gets lost.
Suggestion bots
Suggestions — the best free suggestion box
/suggest posts the idea with ✅/❌ vote buttons. Staff can hold suggestions in a review queue, then resolve each as approved, rejected, implemented or duplicate, with a note; the author gets a DM (docs). Each suggestion can get its own thread, archived when it’s resolved, and posts can be anonymous with up to five images (configuration).
It’s on 88,420 servers according to top.gg, and it’s actively developed: its repository had commits in October 2026. The core is free; Premium is per server, adds things like notifying voters when a suggestion is resolved, and has no published price.
Limits for a studio: duplicates are a manual “Duplicate” resolution, its docs list no export or tracker integration, and it handles ideas, not bug reports with evidence.
Carl-bot — if it’s already in your server
Carl-bot is a general-purpose bot on 3.4 million servers. Its suggestions module takes /suggestion suggest, lets staff approve, deny, consider or implement with a reason, can DM the author on a decision, and moves decided suggestions to a log channel. Suggestions aren’t listed among its Premium features.
Limits: its docs describe no threads, duplicate handling, export or tracker sync. A good fit when you want suggestions handled by a bot you already run, not a separate feedback process.
Ticket bots can do a version of this too: Tickety ships an automation template for a suggestion board members can vote on. If you’re choosing a ticket bot, see our ticket bot comparison.
Bug report bots
Builderman — a structured report wizard
/report and /suggest start a DM wizard: title, scope, game, description and files (command docs). Staff review submissions in a holding channel, accept bugs at low, medium or high severity, reserve them, and /publish posts a game update listing what was fixed (processing reports).
It’s small — 1,116 servers on top.gg — and has no published price. Limits: it blocks archives and executables, which rules out zipped logs and save files, and when staff delete a report, its author isn’t told.
FeedbackBot — simple capture, made for a game
FeedbackBot turns keywords into slash commands (/bug, /idea, /feedback and so on) and copies each submission into a private staff channel where the team can reply. It was first built for the game that became Slay the Spire, where it collected over 22,000 pieces of feedback. It’s free and runs on donations.
Limits: its docs describe no voting, statuses or threads, and the FAQ says export to Jira, Trello or Google Sheets isn’t planned. We found no changelog or other sign of recent updates.
Submitty — the bot with GitHub sync
Submitty handles bug reports and feature requests with optional approval, up / don’t care / down votes, threads, comments and role pings, and it can export open submissions to CSV. On premium it creates a GitHub or GitLab issue for each submission and labels it when a vote threshold is hit. It’s on 2,221 servers (top.gg); the premium price isn’t public.
Limits: the sync is one-way — in its own words, “closing an issue will not close the submission” — so reporters don’t hear about fixes on their own. There’s no Jira.
Bots that come with a tracker or a board
Codecks Decky — for teams already on Codecks
Decky is Codecks’ own bot. Keyword slash commands create entries with an upvote button; once an entry reaches your vote threshold, it becomes a card. Each submission gets a thread synced to the card, team replies reach the reporter as DMs, and players earn karma on a leaderboard. Codecks has a free plan for up to five users, and its pricing page lists additional Decky statuses under the Pro plan.
Limits: it only feeds Codecks, with no Jira or GitHub sync, and the changelog hasn’t mentioned Decky since its 2.0 release in March 2022.
Featurebase — the board that collects inside Discord
Most feedback boards only post notifications to Discord. Featurebase also lets anyone submit with /feedback, and lets admins right-click a message to send it to the board. Using Discord as a feedback source needs its Growth plan, $29 per seat per month billed yearly; end users are unlimited.
Limits: posts that come from Discord “don’t give the authors updates via email”, so Discord reporters don’t hear back, and it’s a feature-request board rather than a bug tracker.
Canny, Feature Upvote and Nolt post board activity into Discord, but players still submit on the web board. Linear’s Discord integration creates issues from Discord, but every user needs a linked Linear account, so it’s a tool for your team, not your players.
Discord’s own Forum channels — the free baseline
A Forum channel gives every report its own thread, and you can require a tag on each post. Tags that only moderators can apply work as statuses, and closing a post locks it. It costs nothing and players already know it.
It needs a Community server. Limits: posts sort by activity or date, not votes; duplicates are merged by hand; a tag change doesn’t notify the reporter; and nothing reaches your tracker. It’s where many communities start, and where most of the bots above plug in.
BetaHub — bugs, suggestions and tickets in one place
BetaHub is a feedback platform for games that includes a Discord bot. It covers more of the path from report to fix than the bots above, and takes more setup.
- Players report where they are.
/report,/suggestand/ticketopen a form in Discord; buttons can be pinned in any channel. Forum threads become reports automatically, and Listen Mode can pick bug-like messages out of the chat channels you point it at. Players don’t sign up anywhere: their Discord account is enough. - Evidence comes with the report.
/reporthas a file field, every report gets an Upload Media button, and when your team needs a screenshot, video or log, the bot asks the reporter in their thread or by DM. - Duplicates are flagged as they arrive. When a new report matches an existing issue, it is merged and the reporter is told so. The issue’s heat score, which ranks what most players hit, rises with every match instead of the queue growing.
- Players hear back. Bug reporters hear about every status change in their thread or by DM, forum threads can show status as tags, and when a bug is fixed, players whose duplicate reports were merged into it are told too.
- Players vote in Discord. A 👍 reaction on a forum thread counts as a vote, no account needed. Suggestions also get a public board, where voting needs a sign-in.
- It reaches your tracker. Paid plans push issues to Jira, GitHub, GitLab, Linear, Asana, ClickUp and others. Status changes sync back from Jira Cloud, GitLab and Linear. With GitHub, a commit that says
fixes #123resolves the issue, but closing it in GitHub doesn’t — the same one-way gap as Submitty. - Beyond Discord. The same project takes reports from Unity, Unreal and Roblox plugins, a web widget and, on the Pro plan, Steam Discussions.
Limits: it’s a platform, not a single bot. Inviting the bot takes minutes, but choosing which channels feed it, which forms players see and how statuses show takes longer than /suggest and done. Tracker integrations and more than one developer need a paid plan, priced per developer seat; players and testers are never billed.
The free plan includes the Discord bot, with 1,000 bug reports, 1,000 suggestions and 1,000 tickets per 30 days across 2 active projects. See the Discord bot and pricing, or the step-by-step guides to setting up the bot and collecting suggestions on Discord.
Side-by-side
| Tool | Votes | Detects duplicates | Tells the reporter | Tracker sync | Price |
|---|---|---|---|---|---|
| Suggestions | Yes | No (manual status) | DM on resolve | No | Free; Premium unpublished |
| Carl-bot | Yes | No | Optional DM | No | Suggestions free |
| Builderman | Yes | No | Public update post | No | Not published |
| FeedbackBot | No | No | Staff reply | No | Free, donations |
| Submitty | Yes | No | Not on GitHub close | GitHub/GitLab, one-way (premium) | Free; premium unpublished |
| Codecks Decky | Yes | No | DMs | Codecks only | Codecks free plan up to 5 users |
| Featurebase | On the board | AI suggestions (Growth) | Not for Discord posts | Jira, Linear, GitHub (Growth) | $29/seat/mo |
| Forum channels | Reactions only | No | No | No | Free |
| BetaHub | 👍 in threads, plus a public board | Yes, merges them | Bug status changes, thread or DM | Two-way: Jira Cloud, GitLab, Linear. One-way: GitHub and more (paid) | Free plan; $26/developer/mo |
Tool details were checked against each vendor’s site in October 2026. Server counts and prices change; follow the links for current numbers.
How to choose
Start from the job, not the bot list:
- Ideas from a community, decided by staff: Suggestions or Carl-bot. Free, familiar, enough.
- Bug reports for a small team that lives in GitHub: Submitty, accepting that closing an issue won’t close the loop with the player.
- A planning tool you already pay for: use its bot — Decky for Codecks, Featurebase if your board is there.
- A live game with an active Discord: you want duplicates merged, evidence attached, players told when things ship, and issues in your tracker. That’s the case BetaHub was built for. The free plan is enough to try it on your own server; tracker sync needs a paid plan, which has a 30-day free trial.
Common questions
Is there a free Discord bot for bug reports?
Yes. Suggestions and Carl-bot are free for suggestions, FeedbackBot is free for capture, and Discord’s Forum channels cost nothing. BetaHub’s free plan includes its Discord bot with 1,000 bug reports per 30 days. The free options differ mostly in what happens after the report: duplicates, statuses and getting it to your tracker.
What happened to Suggester?
Suggester stopped operating on July 19, 2025, and its repository is archived. Its top.gg listing is still up, which is why older lists keep recommending it. Suggestions (suggestions.gg) is the closest active replacement.
How do I get Discord bug reports into Jira or GitHub?
Submitty creates GitHub or GitLab issues on its premium plan. Featurebase’s Growth plan connects to Jira, Linear and GitHub. BetaHub pushes issues to Jira, GitHub, GitLab, Linear and others on paid plans. Status changes sync back from Jira Cloud, GitLab and Linear, and a GitHub commit that says fixes #123 resolves the BetaHub issue; the bug’s reporter then hears about it in their Discord thread or by DM.
Can players report without creating an account?
In Discord, every bot compared here uses the player’s Discord account, so nobody signs up for anything. The difference shows on web boards: voting on BetaHub’s public suggestions board, for example, needs a sign-in.
What does BetaHub cost?
The free plan covers 1,000 bug reports, 1,000 suggestions and 1,000 tickets per 30 days for one developer and 2 active projects, Discord bot included. Paid plans start at $26 per developer per month; players and testers are never billed. See pricing.
Join for free today
Supercharge your team with the best bug tracking and player feedback tools. No credit card required, forever free.
Our Mission
At BetaHub, we empower game developers and communities with an engaging platform for bug submission. We foster collaboration, enhance gaming experiences, and speed up development. BetaHub connects developers, testers, and players, making everyone feel valued. Shape the future of gaming with us, one bug report at a time.
2026 © Upsoft sp. z o.o.