Embed Sentry stack trace in issue

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

Further details

This work supports the Error Tracking Vision.

Proposal

Embed stack trace from a Sentry error when a User creates an issue for the error from GitLab.

Permissions and Security

Documentation

Testing

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

What is the type of buyer?

Links / references

Edited by Sarah Waldner