Skip to content

Healthy Backlog - group::vulnerability research - Add ~"Customer Interest" label

Problem Statement

The Healthy Backlog Initiative - Issue Management Plan (gitlab-org&18639) epic has several mentions of Support to apply the new ~"Customer Interest" label to issues in certain circumstances. We updated our "Working With Issues" workflow to follow this new practice as part of Adjustments to Working With Issues workflow for... (#7009 - closed) and Update label to apply to issues (gitlab-com/content-sites/handbook!15223 - merged)

What is the problem?

We still have existing issues in the gitlab-org group which are labeled ~customer

Why is this a problem?

The existing issues which are labeled ~customer won't be assessed according to the new Healthy Backlog initiative. They should be re-labeled so that they can be considered under that work, and for maintaining the backlog into the future.

Proposal

  • Update open issues for the group groupvulnerability research which are labeled ~customer to add the new ~"Customer Interest" label
  • (optional) discus with the PM and remove the ~customer label. This may be useful meta-information to retain?
  • This could be automated through the GitLab Issues REST API endpoint, or using the glab CLI

DRI

@mmora will act as the DRI for this issue.

Required Resources

  • Talking to the Product Managers for Group
  • Authorized to apply and update labels in GitLab issues (at least Planner or Reporter role in the issues' projects).
  • Access to apply label changes in bulk using the GitLab Issues REST API endpoint, or using the glab CLI

Here is a script to update, as a starting point:

#!/usr/bin/env bash

# Bulk update issues to add label "Customer Interest"
# This uses glab
# Be sure to export GITLAB_TOKEN variable containing your PAT

GROUP="group::vulnerability research"

issues=$(glab issue list          \
  --repo gitlab-org/gitlab        \
  --label customer                \
  --label "${GROUP}"              \
  --output json | jq -r '.[].iid')

for issue in $issues; do
  echo "Adding label to issue #$issue"
  glab issue update $issue        \
    --repo gitlab-org/gitlab 
    --add-label "Customer Interest"
  if [ $? -eq 0 ]; then
    echo "✓ Successfully updated issue #$issue"
  else
    echo "✗ Failed to update issue #$issue"
  fi
done

Potential Roadblocks/Things to consider

In the interest of Efficiency, we might elect to add the new label programmatically, without review by the product managers. This would reduce their involvement to a courtesy communication only.

Desired Outcome

What does success look like?

The new ~"Customer Interest" label will be added to all open issues, with groupvulnerability research, and ~customer labels, as requested by the Healthy Backlog Initiative, so that they can be assessed an managed within the scope of the initiative.

How do we measure success?

Percentage of open issues that have both ~customer and ~"Customer Interest" labels applied, for groupvulnerability research

Issues to review

display: table
title: GitLab Customer issues
description: This view lists Open issues with ~customer labels
fields:
  title,
  labels("type::*") AS "Type", 
  labels("section::*") AS "Section", 
  labels("Group::*") AS "Group",
  labels("Customer*") AS "Cust. Labels",
  epic, milestone, updated
limit: 3
query:
  project = "gitlab-org/gitlab" 
  AND label = "customer" 
  AND label = "group::vulnerability research"
  AND state = opened

Where would future feedback go?

Feedback in this issue, or the parent epic Migrate customer-labelled issues to "Customer I... (&351)

Related Issues/MRs/Epics/Tickets

Edited by Mike Lockhart | GitLab