The missing piece in bug reports
Did you know that most bugs could be reproduced a lot faster if developers could see errors in your console? For a developer, console logs are the closest thing to "looking at your screen over your shoulder". But developers almost never get this info for 2 reasons:
- Unaware: Most people don't even know what console logs are, let alone how to see and report them.
- Forgetfulness: For those who know what console logs are, they still have to remember to open their console, capture a screenshot of the logs, and send it along the bug reports.
No wonder developers rarely get this info!
Introducing automatic console log recording in Marker.io!
Automatic recording of console logs has been one of our most requested feature!
These console logs get attached to any issue submitted and get delivered straight into your issue tracking or project management tool.
Exploring console logs
When a dev opens an issue in Jira, Trello or whatever tool your team uses, there will now be a new mention. This link shows you if there are any relevant console logs for a developer to see. Any errors, warnings and other info will be mentioned in this link.
For developers, this is a great time and energy saver! No more unnecessary back and forth, no more asking for the same things time and time again, and a more efficient workflow.
You can now click this link to see the full console logs as they were on the moment of the capture. It is like freezing the bug in time.
How to get started?
To enable the console logs recording, go to one of your Destination, then go to Widget > Automatic data capture > Console logs.
For optimal result, we recommend that you install your widget via snippet code.
This feature is available on the Team and Company plans. Check here if you have access.