How to radically simplify bug reporting in GitLab
Jan 9, 2019Marie Hargitt

Summary
This post introduces Marker.io as a third-party tool to integrate with GitLab for simplifying bug reporting. It details how Marker.io reduces the reporter's workflow from 10 steps to 3 by capturing and annotating screenshots and sending them directly to a chosen GitLab project. It also highlights the automatic capture of technical environment data (browser, OS, screen size, etc.) within the bug report, making it more actionable for developers. The post contrasts the traditional complex bug reporting process with the streamlined Marker.io workflow.
More from the Bug Triage and Reporting trail
- Shai-Hulud copycat campaign targets Python developers through PyPI typosquatting
- Manage vulnerability noise at scale with auto-dismiss policies
- How to transform compliance observation management with GitLab
- Self-service security alert handling with GitLab's UAM
- How GitLab measures Red Team impact: The adoption rate metric