Quick answer: Make a Trello board with an inbox list plus lists named like Doing and Done, add the Bugnet SDK to your game, and connect the inbox list under Integrate > Integrations > Trello with a Power-Up API key and token. New crashes and in-game player reports are added to the top of the inbox as cards with the report, its details and a link back; when the bug moves to in progress or resolved, the card moves to Doing or Done. It works on every Bugnet plan.
A Trello board with three columns has shipped more indie games than any enterprise tracker. It is quick, visual, and nobody needs training to use it. Where it struggles is intake: every card for a player-reported bug was typed by someone, usually missing the build number and the hardware. This guide keeps the board you like and removes the typing, so crashes and in-game reports show up as cards on their own.
A bug board template that works with automation
Bugnet moves cards by matching list names, so name your lists so it can find them:
| List | Role | Names Bugnet recognises |
|---|---|---|
| Bug inbox | The list you connect. New bugs are added to the top, and reopened bugs return here. | Any name; you pick it when connecting |
| Doing | Where cards go when the bug is marked in progress | Doing, In progress, WIP, Working |
| Done | Where cards go when the bug is resolved, closed or won't-fixed | Done, Complete, Completed, Fixed, Resolved, Shipped, Closed |
Bugnet uses the first open list on the board that matches, so a list called “Fixed in 1.2” works as a Done list too. If no list matches, the card simply stays where it is. Add any other lists you like (Needs repro, Next patch, Backlog); Bugnet leaves cards you move by hand alone until the bug's status changes again.
What each card contains
- Title: the bug's title.
- Description: the report text (for crashes, the error and stack trace), then its details: priority, status, category, platform, game version, occurrence count and who reported it.
- A link back to the report in Bugnet, with the screenshot, the last 100 log lines, and the player's GPU, RAM, OS and resolution.
Setup
1. Capture bugs in the game
Create a free Bugnet project and add the SDK for your engine (Unity, Unreal, Godot, GameMaker, Construct 3, Pygame or web) from the SDK docs. Crashes and errors are captured automatically. Bind the in-game report widget to a key or menu button so players can report the rest.
2. Get a Trello API key and token
- Open trello.com/power-ups/admin, create a Power-Up for your workspace and copy its API key.
- On the same page, follow the Token link, allow access, and copy the token.
3. Connect the inbox list
In Bugnet, open Integrate > Integrations > Trello, paste the API key and token, choose Load lists and pick your inbox list. Then set:
- Add a card for every new bug, or leave it off and send bugs individually from their page.
- Move the card as the bug's status changes.
- Priority filter: all priorities, medium and above, high and above, or critical only.
Choose Connect. Every delivery is logged, failures are retried automatically, and Bugnet checks for an existing card before adding one, so a bug does not get two cards from the same connection.
How the board runs day to day
- Reports arrive already grouped. When fifty players hit the same bug, Bugnet stacks the reports onto one bug with an occurrence count, so your board gets one card.
- Triage on the board. Assign members, add labels and drag cards into your own lists.
- Change status in Bugnet. Status flows from Bugnet to Trello. Marking a bug in progress moves the card to Doing; resolving it moves it to Done, emails the player who reported it (if they left an email), and adds it to your next auto-drafted changelog.
When a board stops being enough
Trello is great until you need answers a board cannot give: how many players hit this, on which builds, did the patch reduce the crash rate, what are Steam reviews saying? Those live in Bugnet regardless of where your cards are: occurrence counts, crash-free sessions per build, a check comparing your two latest versions, and Steam review sync. Many teams keep Trello for planning and use Bugnet for those questions. For a direct comparison, see Bugnet vs Trello for bug tracking; the Trello integration docs cover the details.
Frequently asked questions
Can Trello be used for game bug tracking?
Yes, especially for small teams. A board with an inbox, Doing and Done lists works well, and connecting it to Bugnet means crashes and in-game player reports arrive as cards automatically instead of being typed in by hand.
Which Trello list does a fixed bug move to?
When a bug is resolved, closed or marked won't fix, Bugnet moves its card to the first open list on the board named like Done, Complete, Fixed, Resolved, Shipped or Closed. In-progress bugs move to a list named like Doing, In progress, WIP or Working, and reopened bugs go back to the list they were filed in.
What do I need from Trello to connect it?
A Power-Up API key and a token, both created for your workspace at trello.com/power-ups/admin, plus the board and list you want new bugs added to. On the Bugnet side, the Trello integration is included on every plan, including the free plan.
Will duplicate crashes create duplicate Trello cards?
No. Reports with the same title stack onto one Bugnet bug as occurrences, and Bugnet checks for an existing card before adding one, so each bug gets one card per connection.
Does moving a card in Trello change the bug in Bugnet?
No. Status flows from Bugnet to Trello. Change the bug's status in Bugnet and the card follows.
Keep the board. Lose the copy-paste.