Link to suspect commits in the detail view of Sentry error
Problem to Solve
We can speed up error triage and resolution processes for users by automatically linking them to the commit that caused the error. The commit we are linking to is the suspect commit that Sentry associates with an error based on the GitLab commit SHA sent with the exception.
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
Need to update Sentry error details view to create link to commit that caused an error instead of link to release for the Last seen and First seen field.
Check design.
Make sure that this MR is merged before implementation and we have Sentry instance to check against.
NOTE: Currently GitLab instance returns an error for release tab, so we need either to setup own Sentry test instance or wait till #35084 (closed) is resolved
Documentation
Documentation required, most likely here. I recommend creating a new section for the Error Detail page view that includes a small sub-section on Suspect commits from Sentry and links to their documentation on it.