Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #296787
Closed
Open
Issue created Jan 06, 2021 by Sarah Waldner@sarahwaldner🍉Developer

Slash command to promote issue to incident

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)
  • 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.

Edited Dec 08, 2021 by Alana Bellucci
Assignee
Assign to
Time tracking