Skip to content

Sprint history — Rosters & allocation runs

What shipped

Turning demand + rules into an actual roster.

  • Auto allocation run (MIQ-027) — the run engine: snapshot pre-materialization, the human-gated state machine, candidate evaluation, and rerun.
  • Daily roster report (MIQ-075) — the daily roster report (JSON + xlsx + pdf).
  • Manager landing dashboard (MIQ-080) — the dashboard tiles.
  • Monthly roster calendar view (MIQ-121) — the month-grid roster view.

Key decisions

  • Snapshot pre-materialization — a run scores against a materialized snapshot of eligibility/assignments.
  • Per-rule ineligibility reasons are gated to allocation_run.debug (SYS_ADMIN only) — F6 — the reasons a candidate was excluded exist server-side but only SYS_ADMIN can see them.
  • Equalization tiers + cross-pool reasons are computed server-side but not surfaced in the UI — F8.
  • The web Execute button and the ShiftMix cohort populator are PARTIAL (sheet 09).

Build status

Available (engine + snapshot + state machine + rerun); Partial on some UI surfaces (Execute, ShiftMix) and the F6/F8 reason visibility. See Rosters (concept), Troubleshoot an unfilled run (task), and the Rosters & runs API.

  • Run-detail UX enrichments are tracked under PB-055–061 (Polish backlog).
  • Fact sheets 09 (allocation runs), 17 (reports); reports MIQ-027/075/080/121.