本文由 AI 分析生成
Summary
GitLab Customer Support Operations team’s specific board configurations, covering three boards: Stages (primary workflow board using Stage:: scoped labels), Customers (request origin by team), and Request Type (bug/incident/feature/admin). Boards are used to get workload overview, move issues between stages, and plan iterations.
GitLab 客戶支援運維團隊的三個 issue board 設定：Stages（主要工作流程）、Customers（請求來源）、Request Type（需求分類）。
Key Points
- Primary board is “Stages” — tracks issues through: Triage → Planning → Scheduling → Queued → Deployment → Validation → Implementation → Blocked/Backlogged
- Stage labels are scoped (
Stage::), meaning only one can be active at a time - Customer board uses
Customer::scoped labels to route work by requesting department (Support, Security, Engineering, Finance, People, Field, Marketing) - Request Type board uses
RequestType::labels: Bug, Feature, Incident, Administrative - All boards show both Open and Closed lists with no milestone/iteration/label/assignee filtering
Insights
- This document is a concrete implementation example of the abstract board guidelines — useful as a reference when designing a similar workflow for a new team. The Stage label taxonomy (Triage → Queued → Implementation) is a reasonable starting point for any ops team.
Connections
- Issue and Kanban boards project management guidelines — the general board guidelines this implements
- Labels — the label taxonomy used to drive these boards
- Issues project management guidelines — underlying issue management system
Raw Excerpt
“This is the primary board the Customer Support Operations team works from. It shows all non-closed issues grouped together by the Stage scoped label.”