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,034
    • Issues 38,034
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,347
    • Merge requests 1,347
  • 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
  • #247112

Closed
Open
Created Sep 09, 2020 by Nick Post@npostDeveloper

DevOps adoption MVC (frontend)

This is the frontend implementation issue, the backend implementation issue is #247130 (closed).

Problem to solve

In &4169, we describe the need for a customizable, instance-level DevOps report to understand clusters of adoption across an instance.

  1. Understanding organisational usage - When my organisation is using a new tool; I want to know what parts are being adopted and how they are being used; so that I can understand progress, determine ROI and report to leadership.
  2. Benchmarking across teams - When I have multiple teams in an organisation adopting a tool; I want to understand how each team is using the tool; so that we can understand progress, share learnings and continuously improve.

Proposal

Now

Now Later
Table Screenshot_2020-10-02_at_14.30._2x

Create a data table with expandable rows showing adoption of key features across:

  • Dev
    • Issues: at least 1 issue opened.
    • MRs: at least 1 MR opened.
    • MR approvals: at least 1 approval on an MR.
  • Ops
    • Runner: runner configured for project/group.
    • Pipelines: at least 1 pipeline successfully run.
    • Deploys: at least 1 deploy.
  • Security
    • Scanning: at least 1 security scan of any type run in pipeline.

Additional details:

  • Feature adoption = YES based on usage in the last 30 days
  • Lives in admin area
  • Last updated date in top right hand corner
  • Hovering on dots gives a tooltip saying "Used in the last 30 days"

Later iterations

  1. Add metrics (overarching + stage level) to demonstrate trends & ROI
  2. Introduce "segments" for greater insight into teams
  3. Incorporate DevOps score-type recommendations at group-level
  4. Infinite scroll
Edited Nov 11, 2020 by Nick Post
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking