Jacques Bodin-Hullin is the Founder & CEO of Monsieur Biz, an e-Commerce agency specializing in Sylius.
Before using Marker.io, getting bug reports consistently was a time-consuming headache for both Monsieur Biz and their clients.
Today, the bug reporting process is much faster. Creating new tickets is easier.
This means more issues are reported pre-production—and websites go live quicker (and bug-free!).
Clients don’t have the time to fill out their tickets. And when they do, they miss crucial information every time. With Marker.io, it’s one click. It takes seconds.
The challenge: time-consuming bug reports and too much back-and-forth
Before using Marker.io, the bug reporting process involved:
- Taking a screenshot of the issue
- Opening up an editing tool
- Annotating with details
- Saving the screenshot
- Logging in to Redmine to report the issue
- Adding the screenshot and comments
- etc.
Moreover, because the reports were still incomplete, the Monsieur Biz team would need to get back to the client for details—and so the cycle continued for every report.
Busy eCommerce companies don’t have the time for all of this extra work.Â
With Marker.io, bugs are reported in one click and go straight to Redmine.
Clients gain a ton of time. For devs, each ticket has everything they need, so they save a ton of time, too.
The solution: faster, one-click bug reports
Monsieur Biz implemented Marker.io internally at first. It was easy for the dev team to adopt.
Teaching clients how to use it was also quick and easy.
Marker.io is plugged into every staging and production website. Every bug report contains:Â
- URL and screenshots
- Environment data and console logs
- A session replay showing what happened.Â
Now when an issue arrives, we gain three days of time. We have all the information right away. It’s a win for everybody.
The results
Using Marker.io in combination with the Shape Up methodology was a game-changer for Monsieur Biz.
Clients can report a lot more bugs before go-live, and reports are handled in larger batches of work cycles.
- Tickets now take seconds for clients to create.Â
- Issues are resolved up to 72 hours faster.
- Number of bugs reported in pre-production was multiplied by three.
In a recent project, one of our clients reported a little bit less than 400 tickets. If we multiply 400 by 10 minutes, both for clients and for us… that’s a lot of time saved.
