Skip to content
GitLab
Next
    • Why GitLab
    • Pricing
    • Contact Sales
    • Explore
  • Why GitLab
  • Pricing
  • Contact Sales
  • Explore
  • Sign in
  • Get free trial
  • GitLab.comGitLab.com
  • www-gitlab-comwww-gitlab-com
  • Issues
  • #13294

Create Next Prioritization team dashboards in respective team pages

Objectives

Direction from @meks:

  • Have teams review their backlog & maintain MR hygiene, so the intent is for EMs to embed two dashboards under their respective development team pages in our external handbook.
    • Note: The ones under engineering/metrics are a reference data catalogue. Similar to our global prioritization list partial, they are still SSoT but can be embedded in many places.
  • By standardizing this, we will have a few examples done, and have the remaining done by EMs, with step by step instructions on how to update their handbook pages.
  • Not all team pages currently exist, so we will take this as an opportunity to do handbook structure maintenance. We will take lead on this and point to missing pages since Eng Analytics already has it mapped out

Dashboard

Cross functional backlog dashboard

  • Security issues (pastdue)
  • Infradev issues (pastdue)
  • SUS impacting issues by severity
  • Bugs by severity

MR types dashboard

  • Historical MR types
  • Current month MR types
  • List of recent MRs (2 months)

Team pages

Create the 2 dashboards above

  • From https://about.gitlab.com/handbook/engineering/metrics/
  • To team pages under:
    • https://about.gitlab.com/handbook/engineering/development/dev/
    • https://about.gitlab.com/handbook/engineering/development/sec/
    • https://about.gitlab.com/handbook/engineering/development/ops/
    • https://about.gitlab.com/handbook/engineering/development/fulfillment/
    • https://about.gitlab.com/handbook/engineering/development/growth/
    • https://about.gitlab.com/handbook/engineering/development/enablement/
    • https://about.gitlab.com/handbook/engineering/development/modelops/

Instructions for EMs

Add two links - Team page and MR (see others' examples as listed below)

How?

  1. Add a link to your Team page
  2. Add a link to your MR, which adds two dashboards to your team page using the snippet below or by referencing the model MR. Please make sure to edit your group name in the code. The example below is for the Editor group. Feel free to assign @lmai1 as a reviewer on the MR. (Note that the filter_value parameter is used for the team_group filter in the dashboard)
<%= partial "handbook/engineering/metrics/partials/_cross_functional_dashboard.erb", locals: { filter_value: "Editor" } %>

For managers that manage more than one group, please follow this MR.

Check the box once complete.

Dev Sub-department - @timzallmann

  • devopscreate - @dsatcher
    • Source Code - @sean_carroll
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/create/source-code-be/
      • MR: !104968 (merged)
    • Code Review - @sean_carroll / @andr3
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/create/code-review/backend/
      • MR: !104384 (merged)
    • Integrations - @arturoherrero
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/ecosystem/integrations/
      • MR: !104704 (merged)
    • Editor
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/create-editor/
      • MR: !103803 (merged)
  • devopsmanage - @m_gill
    • Access - @jarka
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/manage/authentication-and-authorization/
      • MR: !104467 (merged)
    • Compliance - @dennis
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/manage/compliance/
      • MR: !104467 (merged)
    • Import - @wortschi
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/manage/import/
      • MR: !104467 (merged) !104375 (merged)
    • Optimize - @blabuschagne
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/manage/optimize/
      • MR: !104467 (merged)
    • Workspace - @mksionek
      • Team page: https://about.gitlab.com/handbook/engineering/development/dev/manage/workspace/
      • MR: !104392 (merged)
  • Gitaly - @andrashorvath
    • Team page: https://about.gitlab.com/handbook/engineering/development/dev/gitaly/
    • MR: !104458 (merged)
  • Project Management - @donaldcook
    • Team page: https://about.gitlab.com/handbook/engineering/development/dev/plan-project-management/
    • MR: !104755 (merged)
  • Product Planning
    • Team page: https://about.gitlab.com/handbook/engineering/development/dev/plan-product-planning-certify-be/#dashboards
    • MR: !103803 (merged)
  • Foundations - @leipert
    • Team page: https://about.gitlab.com/handbook/engineering/development/dev/ecosystem/foundations/
    • MR: !104709 (merged)

Enablement Sub-department - @cdu1

  • Distribution
    • Team page: https://about.gitlab.com/handbook/engineering/development/enablement/distribution/
    • MR: !103803 (merged)
  • Geo
    • Team page: https://about.gitlab.com/handbook/engineering/development/enablement/geo/
    • MR: !103803 (merged)
  • Memory
    • Team page: https://about.gitlab.com/handbook/engineering/development/enablement/memory/
    • MR: !103803 (merged)
  • Global Search
    • Team page: https://about.gitlab.com/handbook/engineering/development/enablement/search/
    • MR: !103803 (merged)
  • Database
    • Team page: https://about.gitlab.com/handbook/engineering/development/enablement/database/
    • MR: !103803 (merged)
  • Sharding
    • Team page: https://about.gitlab.com/handbook/engineering/development/enablement/sharding/
    • MR: !103803 (merged)

Ops Sub-department - @sgoldstein

  • devopsverify - @cheryl.li
    • Pipeline Execution - @marknuzzo
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/verify/pipeline-execution
      • MR: !104265 (merged)
    • Pipeline Authoring - @marknuzzo
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/verify/pipeline-authoring
      • MR: !104265 (merged)
    • Runner - @erushton
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/verify/runner
      • MR: !104265 (merged)
    • Pipeline Insights - @shampton
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/verify/pipeline-insights
      • MR: !104265 (merged)
  • devopsrelease devopsconfigure devopspackage - @dcroft
    • Release - @nicolewilliams
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/release/
      • MR: !104706 (merged)
    • Configure - @nmezzopera
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/configure/
      • MR: !104280 (merged)
    • Package
      • Team page: https://about.gitlab.com/handbook/engineering/development/ops/package/
      • MR: !103803 (merged)
  • Monitor:Respond - @crystalpoole
    • Team page: https://about.gitlab.com/handbook/engineering/development/ops/monitor/respond/
    • MR: !104334 (merged)

Fulfillment Sub-Department - @jeromezng

  • Self-Service Purchase - @rhardarson
    • Team page: https://about.gitlab.com/handbook/engineering/development/fulfillment/
    • MR: !104634 (merged)
  • Billing and Subscription Management - @rhardarson
    • Team page: https://about.gitlab.com/handbook/engineering/development/fulfillment/
    • MR: !104634 (merged)
  • Provision - @jameslopez
    • Team page: https://about.gitlab.com/handbook/engineering/development/fulfillment/
    • MR: !104634 (merged)
  • Utilization - @csouthard
    • Team page: https://about.gitlab.com/handbook/engineering/development/fulfillment/
    • MR: !104634 (merged)
  • Fulfillment Platform - @jameslopez
    • Team page: https://about.gitlab.com/handbook/engineering/development/fulfillment/
    • MR: !104634 (merged)

Growth Sub-Department - @pcalder

  • Activation - ?
    • Team page: [on hold]
    • MR: n/a
  • Adoption - @jayswain
    • Team page: https://about.gitlab.com/handbook/engineering/development/growth/adoption/
    • MR: !104367 (merged)
  • Conversion - @kniechajewicz
    • Team page: https://about.gitlab.com/handbook/engineering/development/growth/conversion/
    • MR: !104342 (merged)
  • Expansion - @kniechajewicz
    • Team page: https://about.gitlab.com/handbook/engineering/development/growth/expansion/
    • MR: !104346 (merged)
  • Product Intelligence - @alinamihaila
    • Team page: https://about.gitlab.com/handbook/engineering/development/growth/product-intelligence/
    • MR: !104368 (merged)

Secure Sub-department - @twoodham

  • Static Analysis - @twoodham
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/secure/static-analysis/
    • MR: !104264 (merged)
  • Dynamic Analysis - @sethgitlab
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/secure/dynamic-analysis/
    • MR: !104261 (merged)
  • Composition Analysis - @gonzoyumo
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/secure/composition-analysis/
    • MR: !104263 (merged)
  • Threat Insights
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/secure/threat-insights/
    • MR: !103803 (merged)
  • Vulnerability Research - @mark.art
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/secure/vulnerability-research/
    • MR: !104789 (merged)

Protect Sub-department

  • Container Security - @nmccorrison
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/protect/
    • MR: !103563 (merged)

Anti-Abuse - @pcalder

  • Anti-Abuse - @jayswain
    • Team page: https://about.gitlab.com/handbook/engineering/development/sec/anti-abuse/
    • MR: !104369 (merged)

ModelOps - @mray2020

  • Applied ML - @mray2020
    • Team page: https://about.gitlab.com/handbook/engineering/development/modelops/appliedml/
    • MR: !104778 (merged)
Edited May 26, 2022 by Cheryl Li
Assignee
Assign to
Time tracking