BugReplay Launches "Feedback by BugReplay"
August 22, 2017

BugReplay announced the availability of “Feedback by BugReplay,” an easy-to-use bug reporting tool that enables users to quickly and accurately submit detailed bug reports about website problems to customer support teams.

Downloadable as a Google Chrome extension, Feedback creates a synchronized screen recording of a website user’s actions, network traffic, JavaScript logs and other key environmental data, reducing the time to complete the task of bug reporting of up to an hour or more to less than a minute.

With Feedback, all users have to do is click on the BugReplay button on their browser, click “record” and then retrace their steps that led to the problem, click on the “record” button again to stop recording, and then click “save” to finish. By recording multiple streams of information and then playing them back simultaneously in an integrated video player, Feedback reproduces in a video clip what tech support would see if they had encountered the problem first-hand.

Tech support staff automatically receive the Feedback video bug report, which captures environmental data about a bug reporter’s browser, operating system, locale, date and time of the report, time zone, system memory and other information. All headers and cookies are saved and displayed alongside the request, so customer support professionals no longer have to ask basic questions like, “Are your cookies enabled?” Screenshot sessions allow users to take unlimited screenshots in one session and edit them with the built-in image editor.

“Feedback by BugReplay is intended for anyone who has a vested interest in a website functioning properly,” said Sam Kaufman, co-founder and CTO of BugReplay. “If you’re dependent on a website for your business and it stops working properly, you need to report the problem to your tech support. By using our Feedback browser extension, reporting a problem will take a lot less time than other methods and your bug report will capture all the information customer support needs to fix the problem quickly.”

“Reporting bugs and replicating the problem for customer support is a very tedious and difficult process, especially when the web user and customer support professional are not sitting right next to each other,” added Kaufman. “People rely on a mix of tools such as screenshots, screen recordings and detailed notes to report bugs, but these are time consuming and offer an incomplete picture at best. Feedback by BugReplay takes these frustrations out of reporting, requires no technical knowledge by the website user and allows tech support to see exactly what went wrong so they can figure out how to fix it quickly.”

Feedback integrates with JIRA, GitHub & Slack and offers custom email integration that will send an email to any address after a report is created. It also integrates with Zendesk so users can attach videos to their support tickets. Users can also share their reports with anyone by creating a shareable URL. The Feedback dashboard lists all reports made so users can easily review reports submitted by anyone within an organization.

The Latest

November 15, 2018

Serverless infrastructure environments are set to become the dominant paradigm for enterprise technology deployments, according to a new report — Why the Fuss About Serverless? — released by Leading Edge Forum ...

November 14, 2018

What to automate? Which parts of the delivery process are good candidates? Which applications will benefit from automation? At first, those sound like silly questions. Automate all your repetitive processes. If you think that you'll do the same thing manually more than once, automate it. Why would you waste your creative potential and knowledge by doing things that are much better done by scripts? Yet, an average company does not adhere to that logic. Why is that? ...

November 13, 2018

I'd love to see more security automation deeply integrated into the development process. Everybody knows since the 1990s that security as an afterthought just doesn't work, yet we keep doing it. The reason, I think, is because it's very hard to automate security ...

November 09, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 5, the final installment, covers deployment and production ...

November 08, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 4 is all about security ...

November 07, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 3 covers the development environment and the infrastructure ...

November 06, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 2 covers the coding process ...

November 05, 2018

Everyone talks about automating the software development lifecycle (SDLC) but the first question should be: What should you automate? With this question in mind, DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 1 starts with by-far the most popular recommendation: Testing ...

October 31, 2018

Halloween is a time for all things spooky, but not when it comes to your mobile app experience. A poor experience can not only scare off your customers but keep them away for good ...

October 30, 2018

As organizations have embraced open source, they have become polyglot — using multiple programming languages and technology stacks to accomplish software and hardware related tasks. Enterprises are caught between the benefits provided by a polyglot environment and the complexities and challenges these environments bring. Ultimately, if the situation remains unchecked, polyglot will kill your enterprise ...

Share this