Link to associated merge request on error detail page

Problem to solve

Determining the root case of an error is time consuming. By linking the user directly to the merge request containing the commit that caused the error, we can save the user time during investigation and restoration of services. Understanding the merge request that introduced the error allows the user to quickly drill into the specific code changes where the error is originating from.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)

Further details

This work supports the Error Tracking Vision.

Proposal

Link to the merge request that caused the error. We should have information on the commit SHA in the exception we get from Sentry. We (hopefully) can determine the merge request from that commit ID. There is another issue open to link errors to associated releases.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.