Skip to content

Labels

Labels

26 labels

  • backlog

    backlog
    Kanban status: Backlog (triaged work awaiting scheduling)

  • blocked

    blocked
    Kanban status: Blocked (waiting on an external dependency or blocker)

  • c(high)

    c(high)
    Complexity High: Cross-cutting architectural or multi-component change

  • c(low)

    c(low)
    Complexity Low: Trivial or localized change

  • c(medium)

    c(medium)
    Complexity Medium: Standard multi-file feature or fix

  • c(very high)

    c(very high)
    Complexity Very High: Major subsystem redesign or multi-silo epic

  • chore

    chore
    Type Chore: Maintenance, dependency, or housekeeping task

  • ci

    ci
    Type CI: Continuous integration, build pipeline, or release automation

  • docs

    docs
    Type Docs: Documentation, runbook, or specification update

  • done

    done
    Kanban status: Done (verified and completed in trunk)

  • epic

    epic
    Type Epic: Parent umbrella initiative coordinating multiple sub-issues

  • feat

    feat
    Type Feat: New user-facing or system capability

  • fix

    fix
    Type Fix: Defect, regression, or bug resolution

  • in progress

    in progress
    Kanban status: In Progress (active implementation in flight)

  • in qa

    in qa
    Kanban status: In QA (merged to integration branch and awaiting verification)

  • in review

    in review
    Kanban status: In Review (pull request open and undergoing review)

  • on hold

    on hold
    Kanban status: On Hold (deferred or paused work item)

  • p0

    p0
    Priority P0: Critical path / blocker requiring immediate resolution

  • p1

    p1
    Priority P1: High priority release or sprint deliverable

  • p2

    p2
    Priority P2: Standard priority planned work item

  • p3

    p3
    Priority P3: Low priority or opportunistic improvement

  • perf

    perf
    Type Perf: Latency, allocation, or throughput optimization

  • ready

    ready
    Kanban status: Ready (specified and ready for implementation)

  • refactor

    refactor
    Type Refactor: Internal code restructuring without behavior change

  • sec

    sec
    Type Sec: Security hardening, vulnerability remediation, or guardrails

  • test

    test
    Type Test: Unit, integration, or end-to-end test coverage