Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • M Metrics
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Support TeamGitLab Support Team
  • Metrics
  • Issues
  • #2
Closed
Open
Issue created Sep 14, 2020 by Lyle Kozloff@lyle🇯🇵Owner

Hypothesis: A single portion of tickets is responsible for the overall sag in FRT

Hypothesis

A single portion of tickets is responsible for the overall sag in FRT.

Evidence gathered

  • SLA per problem type 2020
    • L&R - clearly struggling in all problem types.
    • SaaS ( both general and account ) - are struggling in all problem types - with a few exceptions
    • SM - Secure (SAST, DAST, Scanning, License Management) seems to be the only outlier with over 5% missed SLA.

Conclusions drawn

  1. This hypothesis is not supported by the data: with the exception of Secure in Self-managed, there's no outliers in our current problem types.
  2. We should continue iterating on problem types to get more fine grained data.
Edited Sep 14, 2020 by Lyle Kozloff
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking