本文由 AI 分析生成
Summary
Customer Support Operations team’s milestone usage: one milestone per calendar month representing a deployment period, with a standardized title format (CustSuppOps Deployment YYYY-MM-01) and date range spanning the previous month.
GitLab 客戶支援運維團隊以每月部署為單位建立 Milestone，標題格式固定，起始日期為前一個月的第一天。
Key Points
- Each milestone = one monthly deployment period
- Title format:
CustSuppOps Deployment YYYY-MM-01(four-digit year, two-digit month) - Start date: one month before the title date (e.g., deployment 2025-05-01 → start 2025-04-01)
- Due date: same as the title date
- Milestones are created manually in bulk during the last month of GitLab’s fiscal year (January) for the upcoming year
- Apply milestone via UI sidebar or
/milestone %"TITLE"quick action; remove with/remove_milestone
Insights
- Pre-creating all 12 milestones annually in one batch is a pragmatic operations pattern — it avoids the recurring overhead of milestone creation and ensures consistent naming before any issues are filed.
Connections
- Milestones project management guidelines — general milestone design guidelines
- Issue boards — the Stages board that issues flow through within each milestone
Raw Excerpt
“Each milestone represents one month, from the 1st of one month through the 1st of the next month.”