<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ### Problem to solve We should be able to open an issue based on errors from Sentry, to facilitate triage, track work/progress, and speed up response. The issue will capture all pertinent details of the Sentry error seen on the detail page and allows the user to respond without leaving GitLab. Furthermore, the issue can be used as a way for stakeholders to track and understand status of the problem. The issue can be linked to open support ticket/requests giving Support Engineers a simple way to communicate with customers. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Further details This work supports the [Error Tracking Vision](https://about.gitlab.com/direction/monitor/debugging_and_health/error_tracking/). ### Proposal Add a button to the top section of the [Error Detail page](https://gitlab.com/gitlab-org/gitlab/issues/33838) within GitLab that allows someone to open an issue with an information about the error in it. The MVC could be an issue with a title and description the same as the Sentry error, with a link to the error in Sentry. Further iterations should include a more detailed summary, embedded stack trace, etc. We should consider what issues look like when they are created from Sentry into GitLab. The style and functionality should match. It is ok if this happens in two milestones. ### Design Essentially, this issue involves adding a `Create issue` button to the top of the Error Detail page:  The newly created issue should include the error title and error details (a link to the Sentry event, first/last seen information, the number of events and users impacted). It should also include a stack trace, if possible. Since stack traces can be quite long, the current proposal is to include the first 10 entries of the stack trace, with a show more/show less button as needed: | Show more | Show less| | ------ | ------ | |  |  |