Quick answer: Create a Notion database with properties named Status, Priority, Category, Platform, Version, Report #, Reporter and Bugnet, add a Notion integration to it, and connect it in Bugnet. Every new crash or in-game player report then becomes a page with the full report as its body and the matching properties filled, and the Status property follows the bug as you fix it. The integration is free on every Bugnet plan.
If your design docs, meeting notes and production schedule already live in Notion, a Notion bug tracker is the natural next page. It works well until launch week, when players report bugs faster than anyone can type them in and the useful details (which build, which GPU, what the log said) never make it into the database. This guide gives you a bug database template built for games and shows how to fill it straight from your game.
The Notion bug database template
Create a new full-page database in Notion and give it these properties. The names matter: Bugnet fills properties whose names match its fields, ignoring case, and skips anything it does not recognise, so you are free to add your own properties too.
| Property | Notion type | What gets written | Also matches |
|---|---|---|---|
| Name | Title | The bug's title | Your database's title property |
| Status | Status | Follows the bug: open, in progress, resolved, closed, won't fix | State, Stage |
| Priority | Select | Critical, High, Medium or Low | Severity |
| Category | Select | Crash, Gameplay, Visual and so on | Type, Kind |
| Platform | Select or Text | Windows, Android, Web… | Platforms |
| Version | Text or Select | The game version the report came from | Game version, Build |
| Report # | Number | Bugnet's report number | Report number, Bug # |
| Reporter | Text | The reporter's name, or “Player (anonymous)” | Reported by, Player |
| Bugnet | URL | A link to the full report | Link, URL |
| Description | Text | The start of the report text | Details, Notes, Summary |
The full report always goes into the page body, so the Description property is optional. Create the Priority options (Critical, High, Medium, Low) up front so they are colour-coded the way you like.
How the Status property is set
Notion status properties have three groups: To-do, In progress and Complete. If your Status property has an option named like the bug's status (Open, In progress, Resolved, Closed, Won't fix), Bugnet uses it. Otherwise it picks the first option in the matching group: open bugs go to To-do, in-progress bugs to In progress, and resolved, closed and won't-fix bugs to Complete. That means Notion's default Not started / In progress / Done options work without any changes.
Views worth adding
- Board by Status, the everyday triage view.
- Critical this week: a table filtered to Priority is Critical, sorted by created time.
- By version: a table grouped by Version, for patch-day triage.
- By platform: grouped by Platform, to spot a Steam Deck-only or Android-only problem.
- Mine: add your own Person property called Owner and filter on it. Bugnet leaves properties it does not recognise alone.
Connecting your game to the database
1. Capture bugs in the game
Create a free Bugnet project, add the SDK for your engine from the SDK docs, and initialise it with your API key. Crashes and errors are captured automatically; bind the report widget to a key or pause-menu button so players can report the rest. Each report arrives with a screenshot, the last 100 log lines and the player's platform, OS, GPU, RAM, resolution and game version.
2. Create a Notion integration
Create an internal integration at notion.so/profile/integrations and copy its secret (it starts with ntn_).
3. Give it access to the database
Open your bug database in Notion, choose ••• > Connections and add the integration. Notion integrations only see pages they have been added to.
4. Connect it in Bugnet
In your project, open Integrate > Integrations > Notion, paste the secret, choose Load databases, pick the bug database and set:
- Add a page for every new bug, or leave it off and send bugs individually from their page.
- Update the Status property as the bug changes.
- Priority filter: all priorities, medium and above, high and above, or critical only.
Choose Connect. Deliveries are logged and retried automatically if Notion is briefly unavailable, and Bugnet checks for an existing page before adding one, so each bug is added once per connection.
How the team works day to day
Status flows one way, from Bugnet to Notion, so treat Bugnet as the place a bug's state changes and Notion as the place you plan and discuss:
- A player reports a bug, or the game crashes. Duplicates stack onto one bug in Bugnet with an occurrence count, so Notion gets one page, not fifty.
- The page appears in Notion with the properties filled. Your team assigns it, comments and links it to the relevant design page.
- When the fix ships, resolve the bug in Bugnet. The Notion Status moves to Complete, the player who reported it gets an email if they left one, and the fix shows up in your next auto-drafted changelog.
Why not just type bugs into Notion?
You can, and plenty of teams start that way. The trouble is what gets lost in transcription: the exact build, the GPU, the log lines before the error, the screenshot, and the fact that thirty other players hit the same thing. Our comparison of error tracking vs a Notion bug board goes into the trade-offs. Connecting the two keeps Notion as the planning surface and removes the typing.
The same column matching works for Airtable tables and monday.com boards. Full details are in the integrations docs, and the best bug tracking software for game studios compares Notion with the alternatives.
Frequently asked questions
Can I use Notion as a bug tracker for my game?
Yes. A Notion database with Status, Priority, Category, Platform and Version properties works well as a lightweight bug tracker, especially for teams that already keep their design docs in Notion. The weak point is manual entry, which you can remove by connecting it to a tool that files crashes and player reports automatically.
Which Notion property types does Bugnet fill?
Bugnet writes the bug title into the title property and fills status, select, text, number and URL properties whose names match its fields, such as Status, Priority, Category, Platform, Version, Report #, Reporter and Bugnet or Link. Properties it does not recognise are left alone.
Does changing the status in Notion update Bugnet?
Status flows from Bugnet to Notion. Change the bug's status in Bugnet and the Notion Status property follows, moving between its To-do, In progress and Complete groups.
Will duplicate crash reports create duplicate Notion pages?
No. Reports with the same title stack onto one Bugnet bug with an occurrence count, and Bugnet checks for an existing page before adding one, so each bug is added to Notion once per connection.
Is the Notion integration included in Bugnet's free plan?
Yes. Notion, Airtable, monday.com, Linear, ClickUp, Asana and Trello connections are available on every plan, including the free plan.
Keep Notion for thinking and planning. Let the game do the data entry.