Link to Sentry release on error detail page

Problem to solve

Determining the root case of an error is time consuming. By linking the user directly to the Sentry release from which the error originated, it saves them time when investigating the cause of the error. It also gives the user easy access to roll back the release if the impact is serious enough so that they can quickly restore services for their customers while determining a fix.

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 release that caused error. We should have information on the commit SHA in the exception we get from Sentry. We can determine the release from that commit ID.

Permissions and Security

Documentation

Testing

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

What is the type of buyer?

Links / references