You’re building a great product, but sometimes bugs happen. Asana lets product and engineering teams easily file and track bugs, so they can spend more of their time fixing them. And since you can track all of your work in Asana (not just bugs), you can prioritize bug tracking against other work in a single place.
Follow along with the article to build your own bug tracking project, and take a look at other resources directly below.
|Resources for creating bug tracking projects||Link|
|A short video||Watch How to Asana|
|Asana-created template||Use template|
|An online course||Register for Asana Academy|
How to create a bug tracking project
- Create a new project and name it “Bug tracking.” Assign a Project Owner so they can update the status and monitor bugs as they are reported.
- Add internal team members as project members. When tasks (i.e., reported bugs) are created in the project, project members receive Inbox notifications for each one.
- Assign a teammate a recurring task to go through the bug reports to make sure they get prioritized and assigned.
- Add priority level custom fields by clicking the blue Add Custom Fields link at the top of the project. That way your team knows which bugs to address first.
Build and manage your bug tracking project by following along with with How to Asana.
How to track incoming, new bugs
- If employees are testing the product, have them submit bugs by adding tasks to the bug tracking project.
- Encourage customer-facing teammates to submit customer-reported bugs as tasks.
- If they receive bug reports or issues via email, they can turn them into Asana tasks by going to the project header dropdown and clicking Add Tasks by Email then copying the email address.
- Have employees upload screenshots as an attachment for more context about the bug.
- Use a priority custom fieldcustom field Add more data to Asana tasks. Field names, types, and values are customizable, so you can create fields specifically for your workflow. Read more created above to indicate the level of importance of fixing the bug.
- When you have enough information about the bug, the task can be assigned to an engineer so you know who is working on it.
- When the bug is fixed, you can link to the code change, or any URL, in the comments or task description so everyone involved can see the update.
Tips for managing your bug tracking project
Sort and organize your project with custom fields
You can use custom fields to capture even more information about the bug. You can create custom fields for which feature is affected, browser type, operating system, number of user reports, estimated time to fix, and more. This makes bug reports more uniform, and teammates can more easily report bugs by just selecting from drop-downs or filling out text fields.
You can sort your project by custom fields to see the highest-priority bugs first, or by feature to help you assemble a team around it, instead of trying to tackle everything one by one.
Create a template task
Create a bug reporting template task and encourage teammates to duplicate it, then fill it out so they know exactly what information you need in a bug report.
Bug tracking integrations
There are many Asana integrations for engineering teams, and below are some suggestions for bug tracking. For instructions on how to set up the integrations, head to our apps page.
- Zapier lets you connect Asana to Github so you can add Github issues to Asana as tasks, and vice versa, without having to switch between the apps.
- Instabug and Usersnap allow you to send annotated screenshots directly to Asana as tasks to capture details uniformly and instantaneously.
- Wufoo helps you create a custom web form that feeds information directly into an Asana task. You can capture information about the browser, operating system, or version of the product by adding them as required fields in the form. The webform’s fields can also translate into custom fields in Asana.
Store tasks in multiple projects
You can store bug tracking tasks in multiple projects so work isn’t duplicated and relevant conversations about the bug are in the same place for all stakeholders.
Create separate bug tracking projects
In addition to a general bug tracking project, you can create separate tracking projects for specific products and features. The teams responsible for developing the particular feature can focus on resolving bugs solely related to it.
As you iterate on your product and find bugs, use Asana to track them and smash them.