triage

Name

node-bug:triage

Synopsis

/node-bug:triage [--sub-team core|devices|kueue] [--sprint "OCP Node Core Sprint 42"] [--unassigned-only]

Description

Queries all open bugs in OCPBUGS for Node team components using the "Node Bugs" saved filter, classifies them into triage buckets (Release Blockers, Customer Escalations, Potential Blockers, Component Regressions, Untriaged), routes each bug to the correct sub-team, and suggests assignments based on current workload.

Designed for both interactive triage sessions and headless execution via claude --print.

Implementation

Phase 0: Setup and Argument Parsing

1. Parse Arguments

   • --sub-team core|devices|kueue: Filter results to one sub-team's components. Optional. Read sub-team component lists from the sub-teams table in shared/components.md rather than hardcoding names.
     • core: all Node components not listed under another sub-team
     • devices: components listed under DRA/Devices in the sub-teams table
     • kueue: components listed under Kueue in the sub-teams table
   • --sprint <name>: Filter to bugs in a specific sprint (e.g., "OCP Node Core Sprint 42"). Optional.
   • --unassigned-only: Show only untriaged or unassigned bugs. Optional.

2. Validate Jira Credentials

   Use the authentication chain from the jira reference:

   JIRA_API_TOKEN="${JIRA_API_TOKEN:-$(security find-generic-password -s "JIRA_API_TOKEN" -w 2>/dev/null || secret-tool lookup service redhat key JIRA_API_TOKEN 2>/dev/null)}"
   JIRA_USER="${JIRA_EMAIL:-$(security find-generic-password -s "JIRA_API_TOKEN" -g 2>&1 | grep acct | sed 's/.*="//;s/"//')}"
   : "${JIRA_USER:=$(git config user.email)}"
   [[ "$JIRA_USER" != *@* ]] && JIRA_USER="${JIRA_USER}@redhat.com"
   

   Exit with error if JIRA_API_TOKEN is empty after the chain.

3. Create work directory: mkdir -p .work/node-bug/triage-$(date +%Y-%m-%d)