Yesterday I had a conversation with a web agency friend of mine. The head of the agency and his team were completely annoyed by their bug tracking system. Really difficult to translate into German.
They use Asana for their internal projects and it worked great, so they decided to try it out for bug tracking as well. But they were annoyed to no end! Even though the team had done everything as suggested by Asana in the best practice.
The feedback can basically be summarized as follows:
• The project managers and designers said it took too long to report even simple errors.
• The developers were equally frustrated because the reports were incomplete and inconsistent.
• Asana is great for managing tasks, but it's difficult to create effective bug reports, regardless of position.
Yeah, this is where we come in.
From this, I've identified the five main problems that are preventing your colleagues from creating meaningful bug reports in Asana.
Problem 1: Always switching between Asana and your website to report bugs
Constantly switching back and forth between Asana and your website to provide feedback can be endlessly frustrating, not to mention a serious waste of time.
Even to report the simplest error, you have to go through many steps:
1. find the error
2. take a screenshot of the error
3. open a new browser window
4. log in to Asana
5. select the correct project
6. duplicate the bug report template
7. document the bug
8. add technical information
9. add any screenshots or attachments
10. send the report.
BugShot makes this process much easier. You can: Screenshot the bug and comment on it in one process without leaving the website and directly find and post the next bug.
With a visual feedback tool like BugShot, you save yourself the stress and time. It transforms your complex process into: See bug, capture bug, send bug. Done. It's as simple as that.
Problem 2: Always needing to duplicate the task template to report a bug
To make sure your bug reports contain all the information your tech team needs, Asana recommends using a bug task template and marking it "duplicate". The idea is that you manually copy and fill out the task template each time you want to submit new feedback.
The only problem with this is that your bug reporting process becomes very cumbersome and lengthy.
Not only does your team have to leave the website to report bugs, but they also have to copy the task template and manually add all the information your technical team needs. Then you have to know about the technical stuff and how to get that information. Can you tell me off the top of your head the browser version used, down to the last digit? I can't and I don't want to be able to 😉
Instead, we suggest using a visual feedback tool that sends reports directly from your website, automatically creating a new bug task in BugShot without ever having to duplicate a template or research technical information.
Problem 3: Manually identifying and recording all required technical data
Since websites can react differently depending on the environment, it's an essential part of any bug report.
Always include:
• Browser
• Operating systems (OS) and version
• URL
• Screen size
• Zoomlevel
• Pixel ratio
• Language information
This technical information is super important for your developers as it helps them to recreate the error. If something is missing, it means they have to come back to you and spend a lot of unnecessary time investigating.
With a feedback tool like BugShot, all this technical information is automatically captured for you. Don't worry that you've forgotten something important, it's all there. Automatically.
Problem 4: Insufficient visual contextual information
Visualization is a key aspect of bug reporting. A picture is worth a thousand words, especially when it comes to explaining complex problems. However, Asana does not provide built-in tools for visualizing issues.
With BugShot, you can take screenshots, annotate them and send them directly to your bug tracking project. This takes visual communication to a new level, drastically improving the efficiency and comprehensibility of your bug reports.
Problem 5: Cumbersome communication with the development team
Smooth communication between reporters and developers is crucial for effective bug fixing. However, Asana does not offer specialized communication tools for this.
BugShot, on the other hand, enables seamless communication between all parties involved. Comments, attachments and status can be easily managed within the tool, making it much easier to clarify issues and collaborate.
Problem 6: Approvals
Many tools do not offer any release options for bugs. We have integrated a small option for estimating the time required for bugs and obtaining approval for them via a link.