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
  • Issues
  • #241663

Project 'gitlab-org/monitor/health' was moved to 'gitlab-org/monitor/monitor'. Please update any links and bookmarks that may still have the old path.
Closed
Open
Created Aug 26, 2020 by Sarah Waldner@sarahwaldner✨Developer0 of 6 tasks completed0/6 tasks

Service level Agreement countdown timer for Incidents

Release Notes

Service level agreements are important to keep for customers. Failing to do so can result in lost dollars for the company and a decrease in customer satisfaction and confidence. If you have multiple active incidents, it can be challenging to understand how long the incident has been open and how much time you have remaining to address the problem. The SLA countdown timer allows you to configure the length of your specific SLAs and to see a countdown of time directly on Incidents so that you can make sure you keep your customers happy and meet your SLAs.

Documentation: https://docs.gitlab.com/ee/operations/incident_management/

Problem to solve

Service level agreements are important to keep to customers - failing to do so can results in lost dollars for the company and a decrease in customer satisfaction and confidence. When a Support engineer or Support manager is triaging and delegating multiple incidents at a time, it is difficult to keep an eye on SLAs.

Intended users

  • Devon (DevOps Engineer)
  • Allison (Application Ops)

User experience goal

Support engineer can quickly assess how long an incident has been open and how long they have to meet the Service Level Agreement for customers.

Proposal

Create an attribute on incidents that shows how long an incident has been open and how much time the support team has to meet the SLA.

Have option to add "time to SLA" counter to incident in Settings > Operations Timer appears in the highlight bar when activated Tooltip showing hours and minutes When a user runs out of time, a "SLA exceeded" label and system note are added When the setting is toggled on, surface the "time to SLA" as a column on the incident list
Config When_applied Tooltip Out_of_time Time_to_SLA_column__1_
  • Displaying the "time to SLA" will be linked to a settings checkbox. This checkbox will default to being unchecked.
  • When the "time to SLA" feature has been enabled, a countdown will start from the moment the incident is created, and it will update in 15 minute increments.
  • The "time to SLA" countdown will appear in the highlight bar on incident issue types.
  • When enabled, the "time to SLA" will also show up in the incident list. This column will likely need to be sortable, with the down sort linked displaying incidents nearest to their expiration time at the top of the list. This piece can be part of a separate iteration, if/as needed.

Further details

This works supports the Incident Management Direction.

Permissions and Security

Documentation

Availability & Testing

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

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited Sep 25, 2020 by Sarah Waldner
Assignee
Assign to
13.5
Milestone
13.5 (Past due)
Assign milestone
Time tracking