Scope: medium Risk: medium Spec: partial Type: feature
Summary: SLA Management UI and Configuration — implements the remaining SLA features per ROADMAP.md section 1.5: SLA policy configuration, breach indicators on ticket UI, SLA breach notifications, and fixing the dashboard overdue-count query to use sla_response_due/sla_resolve_due instead of due_date.
Suggestion: This is an empty placeholder — no requirements defined. Based on ROADMAP.md §1.5 and existing infra (SLA columns on Ticket, services/sla.py, dashboard showing overdue count), Phase 3 likely means: (1) SLA policy CRUD (model/schema/routes/frontend page for configuring response/resolve time windows per priority), (2) auto-calculate SLA deadlines on ticket create/update in services/sla.py, (3) SLA breach status display on TicketDetailPage + SLA column on TicketsPage table, (4) optional webhook dispatch on breach, (5) fix dashboard's overdue_sla query to use sla_resolve_due instead of due_date (column doesn't exist on Ticket model). Should define scope with user first since issue body is empty.
Rationale: SCOPE=medium: touches 8-15 files across backend (new model + schema + CRUD + routes + service updates) and frontend (new SLA config page + ticket detail/list updates). RISK=medium: fixes the dashboard overdue query which has been using a non-existent Ticket.due_date column (query silently returns 0?), and the SLA breach notification could affect existing ticket workflows. SPEC=partial: ROADMAP.md §1.5 lists SLA enhancements as Phase 1 Q2 2026, which aligns with this issue's title, but the roadmap has no detailed spec for the implementation, and the issue body is empty. TYPE=feature: adding new GUI and configuration capability for SLA management.

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=medium, risk=medium, spec=partial --- **Scope:** medium **Risk:** medium **Spec:** partial **Type:** feature **Summary:** SLA Management UI and Configuration — implements the remaining SLA features per ROADMAP.md section 1.5: SLA policy configuration, breach indicators on ticket UI, SLA breach notifications, and fixing the dashboard overdue-count query to use sla_response_due/sla_resolve_due instead of due_date. **Suggestion:** This is an empty placeholder — no requirements defined. Based on ROADMAP.md §1.5 and existing infra (SLA columns on Ticket, services/sla.py, dashboard showing overdue count), Phase 3 likely means: (1) SLA policy CRUD (model/schema/routes/frontend page for configuring response/resolve time windows per priority), (2) auto-calculate SLA deadlines on ticket create/update in services/sla.py, (3) SLA breach status display on TicketDetailPage + SLA column on TicketsPage table, (4) optional webhook dispatch on breach, (5) fix dashboard's overdue_sla query to use sla_resolve_due instead of due_date (column doesn't exist on Ticket model). Should define scope with user first since issue body is empty. **Rationale:** SCOPE=medium: touches 8-15 files across backend (new model + schema + CRUD + routes + service updates) and frontend (new SLA config page + ticket detail/list updates). RISK=medium: fixes the dashboard overdue query which has been using a non-existent Ticket.due_date column (query silently returns 0?), and the SLA breach notification could affect existing ticket workflows. SPEC=partial: ROADMAP.md §1.5 lists SLA enhancements as Phase 1 Q2 2026, which aligns with this issue's title, but the roadmap has no detailed spec for the implementation, and the issue body is empty. TYPE=feature: adding new GUI and configuration capability for SLA management. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.

Mark added

triage-approved

and removed

blocked:needs-decision

labels

2026-05-28 07:18:38 +00:00

Mark added

blocked:gate-plan

and removed

triage-approved

labels

2026-05-29 18:24:38 +00:00