Embed sentry stack trace in Error Detail page

Problem to solve

We want to reduce context switching and copy/pasting screenshots as much as possible during triage and response workflows. If users can create issues for critical errors in GitLab, we want them to have enough context that does not require them immediately jumping out of GitLab and back into Sentry.

The stack trace is a critical part of determining where in code something is going wrong and how to fix it. Embedding it in a GitLab issue would allow the User to remain in one tool with familiar workflows and UX, speeding up resolution.

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

Embed Sentry stack trace in the Error Detail page. We need to determine:

• If we are able to embed the sentry stack trace in a file diff UI as seen in the mockup below
• Level of effort and feasibility of having multiple level stack traces as seen in Sentry (eg. https://sentry.gitlab.net/gitlab/gitlabcom/issues/998766/?query=is:unresolved)