Skip to content

docs(runbooks): record priority band definitions in triage #545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ss-o merged 1 commit into from
Aug 27, 2026
Merged

docs(runbooks): record priority band definitions in triage #545

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions runbooks/triage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,19 @@ The organization label set in `lib/labels.yml` is the source of truth. Apply at
| duplicate | `duplicate` |
| not planned | `wontfix` |

### Priority definitions

Apply `priority:high` only for the top two bands. Everything below is tracked by
project-board `Priority` rather than by a label.

| Priority | Meaning |
| ------------ | -------------------------------------------------------------------------- |
| **Critical** | Data loss, security vulnerability, or complete breakage with no workaround |
| **High** | Significantly impacts users or blocks important work; schedule next |
| **Medium** | Important but not urgent; prioritize against other planned work |
| **Low** | Nice to have; no fixed timeline |
| **None** | Not yet triaged or genuinely optional |

## Step 3 — Cross-reference

Before responding:
Expand Down
Loading