Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 38,037
    • Issues 38,037
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,345
    • Merge requests 1,345
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Merge requests
  • !42358

Merged
Created Sep 15, 2020 by Vitali Tatarintev@ck3gMaintainer7 of 13 tasks completed7/13 tasks

Add system note on change incidents severity

  • Overview 42
  • Commits 6
  • Pipelines 7
  • Changes 17

What does this MR do?

Adds a system note every time an incident's severity updated.

Info: The functionality is hidden behind a add_severity_system_note feature flag. Run Feature.enable(:add_severity_system_note, true) from Rails console to enable it on your localhost.

Feature flag rollout issue: #251110 (closed)

Screenshots

Screenshot_2020-09-17_at_10.09.44

Demo

Don't mind the old icon in the demo.

Severity_SystemNote_Demo

Does this MR meet the acceptance criteria?

Conformity

  • Changelog entry
  • Documentation (if required)
  • Code review guidelines
  • Merge request performance guidelines
  • Style guides
  • Database guides
  • Separation of EE specific content

Availability and Testing

  • Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
  • Tested in all supported browsers
  • Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited Sep 18, 2020 by Vitali Tatarintev
Assignee
Assign to
Reviewer
Request review from
13.5
Milestone
13.5 (Past due)
Assign milestone
Time tracking
Source branch: ck3g-add-system-note-on-change-severity