Why we scoped down to build up error tracking

What this post added

This post details the iterative development process for GitLab's error tracking feature. It outlines the product strategy for error tracking, breaking it down into epics for instrumentation, correlation, resolution, and triaging. Specifically, it highlights the development of a 'Create an Issue' button from Sentry error details, which was implemented in three frontend iterations and supported by backend work to associate issues with errors and prevent duplicates. The post emphasizes the benefits of iterative development, including faster shipping of value and increased merge request rates.