Quick answer: Add the Bugnet SDK to your game, then connect an Asana project under Integrate > Integrations > Asana with a personal access token. Each new crash or in-game player report (or only those above a priority you choose) becomes an Asana task with the report, its details and a link back. Resolving, closing or won't-fixing the bug completes the task; reopening the bug reopens it. It works on every Bugnet plan.
Asana is a common home for studios where producers, artists and marketing plan alongside programmers. Bugs tend to be the awkward part: they arrive in Discord, Steam reviews and crash logs, and someone has to copy them into tasks. This guide connects your game to Asana so that step disappears.
How it works
- The game captures the bug. Bugnet's SDK files crashes and errors automatically, and players report the rest from an in-game widget. Each report includes a screenshot, platform, OS, GPU, RAM, resolution and build, and crashes add the stack trace and recent log lines.
- Bugnet groups it. Reports with the same title stack onto one bug with an occurrence count.
- Asana gets a task in the project you chose, carrying the report text, its details (priority, status, category, platform, version, occurrences, reporter) and a link to the full report.
- The task follows the bug. Resolved, closed or won't fix completes it; reopened reopens it.
Setup
1. Add Bugnet to your game
Create a free Bugnet project, copy its API key and add the SDK for your engine (Unity, Unreal, Godot, GameMaker, Construct 3, Pygame or web; see the SDK docs). Bind the report widget to a key or menu button.
2. Create an Asana personal access token
In Asana's developer console (app.asana.com/0/my-apps), create a personal access token. Consider using a shared bot account so tasks are not tied to one person.
3. Connect the project
In Bugnet, open Integrate > Integrations > Asana, paste the token, choose Load projects and pick the project. Then choose:
- Create a task for every new bug, or leave it off and send chosen bugs from their page.
- Complete or reopen the task with the bug.
- Priority filter: all priorities, medium and above, high and above, or critical only.
Choose Connect. Deliveries are logged and retried automatically, and Bugnet checks for an existing task before creating one, so retries do not duplicate tasks.
An Asana project layout that works for bugs
- Sections: Incoming, Triaged, In progress, Ready to test. New tasks arrive in the project; your team moves them through sections as they work.
- Custom fields you fill during triage, such as Build or Owner discipline. The report's details are already in each task's description.
- Rules in Asana to assign incoming tasks to a triage owner.
Day to day
Status flows from Bugnet to Asana, so change a bug's status in Bugnet. Resolving it completes the Asana task, emails the player who reported it (if they left an email) and adds the fix to your next auto-drafted changelog. Keep the filter at high and above if you want Asana to hold only committed work, and send lower-priority bugs across when they earn a slot.
Prefer a different planner? The same connection exists for ClickUp, Trello, Linear and monday.com.
Frequently asked questions
Can Asana be used for game bug tracking?
Yes. An Asana project with sections for incoming, triaged and in-progress bugs works well, and connecting it to Bugnet means crashes and player reports become tasks automatically.
What happens to the Asana task when a bug is fixed?
Resolving, closing or marking the bug won't fix in Bugnet completes the Asana task. Reopening the bug reopens the task.
Will repeat crashes create duplicate Asana tasks?
No. Repeat reports with the same title stack onto one Bugnet bug, and Bugnet checks for an existing task before creating one.
Which Asana token does Bugnet need?
A personal access token created in Asana's developer console.
Is the Asana integration free?
Yes. It is included on every Bugnet plan, including the free plan.
Asana is where the plan lives. Let the game, not a person, decide what shows up in it.