Project Labels Strategy | Better Filtering & Clarity
Create effective project labels with GitScrum for type, priority, and component. Enable powerful filtering and automation. Clear categorization without complexity.
4 min read
Labels add metadata that makes boards searchable and filterable, but too many labels create confusion. GitScrum's label system supports clear categorization by type, priority, component, and workflow stage—enabling quick filtering and column automation without label overload.
Label Strategy
Purpose-Driven Labels
LABEL CATEGORIES:
┌─────────────────────────────────────────────────────────────┐
│ ORGANIZING LABELS BY PURPOSE │
├─────────────────────────────────────────────────────────────┤
│ │
│ TYPE LABELS (what kind of work): │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ type:feature ││
│ │ type:bugfix ││
│ │ type:tech-debt ││
│ │ type:documentation ││
│ │ type:research ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ PRIORITY LABELS (how urgent): │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ priority:p1-critical ││
│ │ priority:p2-high ││
│ │ priority:p3-medium ││
│ │ priority:p4-low ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ COMPONENT LABELS (where in codebase): │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ component:frontend ││
│ │ component:backend ││
│ │ component:api ││
│ │ component:database ││
│ │ component:mobile ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ STATUS LABELS (workflow state): │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ status:blocked ││
│ │ status:needs-review ││
│ │ status:needs-design ││
│ │ status:ready ││
│ └─────────────────────────────────────────────────────────┘│
│ │
└─────────────────────────────────────────────────────────────┘
Label Best Practices
Do's and Don'ts
| Do | Don't |
|---|---|
| Use consistent naming | Random label names |
| Limit to ~15-20 labels | 50+ labels |
| Use prefixes (type:, priority:) | Flat, unprefixed labels |
| Review labels quarterly | Never clean up |
| Document label meanings | Assume everyone knows |
Label Automation
Column-Based Auto-Labels
AUTOMATED LABELING:
┌─────────────────────────────────────────────────────────────┐
│ LABELS APPLIED BY COLUMN RULES │
├─────────────────────────────────────────────────────────────┤
│ │
│ COLUMN: "Ready for Development" │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ → Add label: "status:ready" ││
│ │ → Clear label: "status:needs-design" ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ COLUMN: "In Development" │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ → Add label: "status:in-progress" ││
│ │ → Clear label: "status:ready" ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ COLUMN: "Code Review" │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ → Add label: "status:needs-review" ││
│ │ → Clear label: "status:in-progress" ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ COLUMN: "Done" │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ → Add label: "status:completed" ││
│ │ → Clear label: "status:needs-review" ││
│ └─────────────────────────────────────────────────────────┘│
│ │
└─────────────────────────────────────────────────────────────┘
Filtering with Labels
Common Filter Patterns
| Filter | Purpose |
|---|---|
| type:bugfix | View all bugs |
| priority:p1-critical | Urgent items only |
| component:frontend | Frontend team work |
| status:blocked | See blockers |
| type:tech-debt + priority:p2 | High-priority debt |
Label Documentation
Creating a Label Guide
LABEL DOCUMENTATION:
┌─────────────────────────────────────────────────────────────┐
│ NOTEVAULT LABEL GUIDE │
├─────────────────────────────────────────────────────────────┤
│ │
│ NOTE: "Project Label Guide" │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ## Type Labels ││
│ │ - type:feature → New functionality ││
│ │ - type:bugfix → Defect repair ││
│ │ - type:tech-debt → Code improvement ││
│ │ ││
│ │ ## Priority Labels ││
│ │ - priority:p1-critical → Production issue, immediate ││
│ │ - priority:p2-high → Fix this sprint ││
│ │ - priority:p3-medium → Next sprint ││
│ │ - priority:p4-low → When convenient ││
│ │ ││
│ │ ## When to Apply ││
│ │ - Every task must have exactly one type: label ││
│ │ - Every task should have a priority: label ││
│ │ - Component labels optional but recommended ││
│ │ - Status labels applied automatically by columns ││
│ └─────────────────────────────────────────────────────────┘│
│ │
└─────────────────────────────────────────────────────────────┘