Quick answer: Add the Bugnet SDK to your game, then connect a monday.com board under Integrate > Integrations > monday.com with your API token. Each new crash or in-game report creates an item with the report posted as its first update; the board's Status column follows the bug, a status column titled Priority gets the priority, and text or link columns named like Bugnet's fields are filled. Included on every Bugnet plan.
monday.com is popular with studios where production, marketing and live operations share one workspace. Bugs from a live game rarely make it onto those boards in good shape: they are copied from Discord or Steam reviews without the build, the device or the logs. This guide connects your game directly to a monday.com board.
Board setup
Create a board for bugs with these columns. Bugnet matches columns by name and skips anything it does not recognise.
| Column | Type | What Bugnet does |
|---|---|---|
| Item name | Name | The bug's title |
| Status | Status | Follows the bug: Working on it, Done, Won't fix, Reopened |
| Priority | Status column titled “Priority” | Critical, High, Medium or Low |
| Platform, Version, Report #, Reporter | Text | Filled from the report |
| Bugnet | Link | A link to the full report |
The full report (with the stack trace for crashes) is posted as the item's first update, so the conversation about the bug starts with all the context.
Connecting it
- Capture bugs in the game. Create a free Bugnet project and add the SDK for your engine. Crashes are captured automatically with logs, a screenshot and hardware details, and players report the rest from an in-game widget.
- Copy your monday.com API token from your avatar menu under Developers > My access tokens.
- Connect the board. In Bugnet, open Integrate > Integrations > monday.com, paste the token, choose Load boards and pick your bug board.
- Choose the behaviour: create an item for every new bug (or only those above a priority), and update the Status column as the bug changes. Choose Connect.
Working with it
- One item per bug. Repeat reports stack onto one Bugnet bug, so a crash hit by hundreds of players is a single item; the occurrence count is in Bugnet.
- Status flows from Bugnet. Change a bug's status in Bugnet and the board follows. Resolving it also emails the player who reported it (if they left an email) and feeds your changelog.
- Automations still work. Use monday.com automations on the items Bugnet creates, for example to assign new critical items to your live-ops lead.
- Retries are automatic. Deliveries are logged, failed ones are retried, and Bugnet checks for an existing item before creating one.
Using another planner? See the guides for Asana, Airtable and ClickUp.
Frequently asked questions
Can monday.com be used for game bug tracking?
Yes. A board with Status and Priority columns works well, and Bugnet can create an item for each new crash or player report automatically.
Where does the bug report appear in monday.com?
The item is named after the bug, and the full report is posted as the item's first update. Matching columns such as Platform, Version and a Bugnet link are filled.
How does the Priority column work?
Give the board a status column titled Priority. Bugnet sets it to the bug's priority.
Will repeat crashes create duplicate items?
No. Repeat reports stack onto one Bugnet bug, and Bugnet checks for an existing item before creating one.
Is the monday.com integration free?
Yes. It is included on every Bugnet plan, including the free plan.
Put the bug where the studio already looks, with everything needed to fix it already attached.