Configuring Organization-Wide Labels

Inconsistent labels across projects create confusion and make cross-project reporting impossible. Organization-wide labels in GitScrum ensure everyone uses the same vocabulary, enabling powerful filtering, automation, and reporting that works everywhere.

Label Chaos vs Order

Label Taxonomy

Recommended Structure

ORGANIZATION LABEL STRUCTURE
════════════════════════════

PRIORITY:
├── priority:critical  (🔴 Red)
├── priority:high      (🟠 Orange)
├── priority:medium    (🟡 Yellow)
└── priority:low       (🔵 Blue)

TYPE:
├── type:bug           (🔴 Red)
├── type:feature       (🟢 Green)
├── type:improvement   (🔵 Blue)
├── type:chore         (⚪ Gray)
├── type:docs          (📘 Purple)
└── type:security      (🟣 Purple)

STATUS:
├── status:blocked     (🔴 Red)
├── status:needs-review (🟡 Yellow)
├── status:in-progress  (🔵 Blue)
└── status:on-hold     (⚪ Gray)

AREA:
├── area:frontend      (🔵 Blue)
├── area:backend       (🟢 Green)
├── area:api           (🟣 Purple)
├── area:infrastructure (🟠 Orange)
└── area:mobile        (🩵 Cyan)

EFFORT:
├── effort:xs          (tiny)
├── effort:s           (small)
├── effort:m           (medium)
├── effort:l           (large)
└── effort:xl          (extra large)

Naming Conventions

LABEL NAMING RULES
══════════════════

FORMAT: category:value

GUIDELINES:
├── Use lowercase
├── Use hyphens for multi-word
├── Prefix with category
├── Keep values short
├── Be descriptive
└── Avoid abbreviations

GOOD:
├── priority:high
├── type:bug
├── status:needs-review
├── area:user-auth
└── team:platform

BAD:
├── HIGH PRIORITY
├── BUG
├── NR
├── auth
└── Platform Team

Configuration Setup

Organization Settings

ORGANIZATION LABEL CONFIG
═════════════════════════

SETTINGS → ORGANIZATION → LABELS

Label Groups:
┌───────────────────────────────────────────────┐
│  Group: Priority                              │
│  ─────────────────                            │
│  Required: Yes (one per task)                 │
│  Default: priority:medium                     │
│                                               │
│  Labels:                                      │
│  ├── 🔴 priority:critical                    │
│  ├── 🟠 priority:high                        │
│  ├── 🟡 priority:medium                      │
│  └── 🔵 priority:low                         │
│                                               │
│  [Add Label] [Edit Group]                     │
└───────────────────────────────────────────────┘

Syncing to Projects

LABEL SYNC CONFIGURATION
════════════════════════

SYNC OPTIONS:
├── Automatic: Labels sync to all projects
├── Selective: Choose which projects
└── Override: Project can add local labels

PROJECT SETTINGS:
┌───────────────────────────────────────────────┐
│  Organization Labels                          │
│  ─────────────────                            │
│  ✓ Sync organization labels                   │
│  ✓ Allow project-specific labels              │
│  ✗ Allow editing organization labels          │
│                                               │
│  Active Organization Labels: 23               │
│  Project-Specific Labels: 3                   │
└───────────────────────────────────────────────┘

Using Labels Effectively

Filtering and Search

LABEL-BASED FILTERING
═════════════════════

SINGLE LABEL:
└── label:priority:high

MULTIPLE LABELS (AND):
└── label:priority:high label:type:bug

MULTIPLE LABELS (OR):
└── label:priority:high,priority:critical

EXCLUDE:
└── -label:status:on-hold

COMBINED QUERY:
└── label:type:bug label:priority:high -label:status:blocked

SAVED FILTERS:
├── "Critical Bugs" → type:bug + priority:critical
├── "My Work" → assignee:me + status:in-progress
└── "Blocked Items" → status:blocked

Cross-Project Reporting

ORGANIZATION-WIDE REPORTS
═════════════════════════

DASHBOARD QUERY:
"All high-priority bugs across organization"

Filter:
├── Organization: All projects
├── Labels: type:bug + priority:high
└── Status: Not done

RESULT:
┌────────────────────────────────────────────────┐
│  High Priority Bugs Across Org                 │
├────────────────────────────────────────────────┤
│  Project Alpha  │  5 bugs   │  Oldest: 3 days  │
│  Project Beta   │  2 bugs   │  Oldest: 1 day   │
│  Project Gamma  │  8 bugs   │  Oldest: 7 days  │
│  ────────────────────────────────────────────  │
│  Total          │  15 bugs  │                  │
└────────────────────────────────────────────────┘

Automation Rules

LABEL-BASED AUTOMATION
══════════════════════

RULE 1: Priority Escalation
─────────────────────────────────────
Trigger: Task labeled priority:critical
Actions:
├── Assign to on-call team
├── Notify #critical-alerts
├── Set SLA to 4 hours
└── Add to Priority Dashboard

RULE 2: Bug Triage
─────────────────────────────────────
Trigger: Task labeled type:bug
Actions:
├── Add to Triage board
├── Set default priority:medium
├── Notify QA team
└── Add triage checklist

RULE 3: Review Required
─────────────────────────────────────
Trigger: Task labeled needs-review
Actions:
├── Notify reviewers
├── Add to review queue
└── Set 24h reminder

Governance

Label Management

LABEL GOVERNANCE
════════════════

ADDING NEW LABELS:
├── Request via form/issue
├── Review by admin
├── Check for duplicates
├── Consistent naming
└── Announce to org

DEPRECATING LABELS:
├── Mark as deprecated
├── Migration period
├── Auto-replace if possible
├── Remove after 30 days
└── Update documentation

LABEL OWNERS:
├── Each category has owner
├── Owner approves changes
├── Owner trains on usage
└── Quarterly review

Documentation

LABEL DOCUMENTATION
═══════════════════

LABEL GUIDE STRUCTURE:
├── Category overview
├── When to use each label
├── Examples
├── Common combinations
└── What NOT to use

EXAMPLE:
─────────────────────────────────────
## priority:critical

Use when:
- Production is down
- Security vulnerability
- Data loss possible
- Revenue-impacting

Don't use for:
- "Urgent" client requests
- Personal importance
- Nice-to-haves

SLA: 4 hours response, 24 hours resolution
─────────────────────────────────────

Best Practices

For Organization Labels

1. Start minimal — Add labels as needed
2. Document everything — Labels are useless if undefined
3. Enforce consistency — Review usage regularly
4. Enable automation — Labels should trigger actions
5. Train the team — Onboarding includes label guide

Anti-Patterns

LABEL MISTAKES:
✗ Too many labels (>50)
✗ No naming convention
✗ Duplicate meanings
✗ Labels nobody uses
✗ No documentation
✗ Per-project variations
✗ No governance process

Related Solutions

• Automating workflow transitions with labels
• Creating effective filtering systems
• Managing work across multiple projects