This guide standardizes severity labels and SLAs for Plan Manager issues.
- type:bug — defect in behavior
- type:enhancement — improvement or polish
- type:docs — documentation only
- area:* — component or subsystem (e.g., area:tools, area:server, area:docs)
- needs-info — missing reproduction or details
\n+Performance topics: use
area:performancein addition totype:enhancementunless there is a clear functional defect (then usetype:bug).
- P0 — Crash/data loss/security; blocks primary flows.
- P1 — Broken but with workaround; major UX or correctness impact.
- P2 — Minor issue/polish; does not block shipping. \n+Examples:
- P1: Feature works but is unacceptably slow for typical inputs; or incorrect output with readily available workaround.
- P2: Minor latency regression in non-critical path; cosmetic misalignment.
- P0 — Acknowledge: 24h; Fix: 72h or hotfix plan.
- P1 — Acknowledge: 48h; Plan/Fix: within one iteration.
- P2 — Batch and address during polish windows.
- Initial: apply labels, set P0/P1/P2, add repro steps or mark needs-info.
- Weekly: review new/untriaged items; re-evaluate severities; assign owners.
- Schedule: every Monday, 10:00 UTC (adjust as needed for your team).
- Participants: maintainer + last week’s contributors.
- Reminders: calendar event and chat reminder 15 minutes before start.
- Outcomes: updated labels/severities, explicit owner per P0/P1, "needs-info" pings sent.
Suggested agenda (≤15 minutes):
- Scan new items → label + severity.
- Review open P0/P1 → confirm owners and ETAs.
- Sweep needs‑info → send/refresh pings; close stale if justified.
- Saved views for: P0 open, P1 open, needs-info, and by area.
- Plan overview: run
report plan. - Backlog by priority: run
list_tasksand scan forpriority(0 is highest). - Needs‑info and area: reflect labels in titles/descriptions; group via stories.
Note: First‑class filters are planned in future iterations.