### Release notes Sometimes after time and effort have been invested in an issue, the participants realize that the problem to be solved needs to be escalated to an incident. Leveraging slash commands, a known paradigm in GitLab, would allow them to promote the issue to an incident seamlessly while maintaining all of the context and discussion on the same record. https://docs.gitlab.com/ee/user/project/quick_actions.html#issues-merge-requests-and-epics ### Problem to solve Sometimes after time and effort have been invested in an issue, the participants realize that the problem to be solved needs to be escalated to an incident. Leveraging slash commands, a known paradigm in GitLab, would allow them to promote the issue to an incident seamlessly while maintaining all of the context and discussion on the same record. ### Intended users * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) ### User experience goal User can promote an issue to an incident using a slash command ### Proposal Create slash command called `/promote-to-incident`. This will change the type of the issue from an issue to an incident.