Mark/msp_c2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[Phase 1] SLA Management UI and Configuration — Phase 8: 5. SLA UI #39

New issue
Closed
opened 2026-05-28 00:52:39 +00:00 by Mark · 2 comments
Mark commented 2026-05-28 00:52:39 +00:00
Owner
Copy link

Phase 8: 5. SLA UI

  • SLA policy configuration page (admin)
  • SLA status indicators on tickets
  • SLA report page

Decomposed from msp_c2#10

## Phase 8: 5. SLA UI - SLA policy configuration page (admin) - SLA status indicators on tickets - SLA report page --- _Decomposed from [msp_c2#10](https://forgejo.tail018ac4.ts.net/Mark/msp_c2/issues/10)_
Mark commented 2026-05-28 03:51:56 +00:00
Author
Owner
Copy link

⏸ Needs Decision

Blocking factors:

  • Didn't meet auto-approve criteria — scope=medium, risk=low, spec=aligned

Scope: medium Risk: low Spec: aligned Type: feature
Summary: Build the SLA management UI covering admin policy configuration, ticket-level SLA breach indicators, and an SLA report page.
Suggestion: Build incrementally: (1) SLA policy model/schema + CRUD API routes under /api/v1/sla-policies, (2) embed SLA breach state in existing ticket GET responses via the services/sla.py detection logic, (3) admin-only SLA policies config page (frontend), (4) SLA status badges on TicketsPage table + TicketDetailPage header, (5) SLA report page with filterable breach history, (6) navigation link in Layout.jsx for admin users.
Rationale: Medium scope because it adds a new subsystem (SLA policies model + CRUD + 3 new pages + modifications to 3 existing pages/files) across ~12-15 files total. Risk is low because it's purely additive (new table, new endpoints, new pages) — no existing paths are modified except adding SLA indicators to ticket display. Fully aligned with the Phase 8 SLA epic decomposed from the project roadmap. Backend detection logic and DB columns already exist, so this is a UI+policy layer on top of existing foundation.

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=low, spec=aligned --- **Scope:** medium **Risk:** low **Spec:** aligned **Type:** feature **Summary:** Build the SLA management UI covering admin policy configuration, ticket-level SLA breach indicators, and an SLA report page. **Suggestion:** Build incrementally: (1) SLA policy model/schema + CRUD API routes under /api/v1/sla-policies, (2) embed SLA breach state in existing ticket GET responses via the services/sla.py detection logic, (3) admin-only SLA policies config page (frontend), (4) SLA status badges on TicketsPage table + TicketDetailPage header, (5) SLA report page with filterable breach history, (6) navigation link in Layout.jsx for admin users. **Rationale:** Medium scope because it adds a new subsystem (SLA policies model + CRUD + 3 new pages + modifications to 3 existing pages/files) across ~12-15 files total. Risk is low because it's purely additive (new table, new endpoints, new pages) — no existing paths are modified except adding SLA indicators to ticket display. Fully aligned with the Phase 8 SLA epic decomposed from the project roadmap. Backend detection logic and DB columns already exist, so this is a UI+policy layer on top of existing foundation. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.
Mark commented 2026-06-08 05:47:58 +00:00
Author
Owner
Copy link

All SLA UI files (SLAPolicyPage.jsx, SLAStatusBadge.jsx, SLAReportPage.jsx, SLANotificationsPage.jsx, SLA components) were committed under #37 and #40. Code already exists and is deployed. Closing.

All SLA UI files (SLAPolicyPage.jsx, SLAStatusBadge.jsx, SLAReportPage.jsx, SLANotificationsPage.jsx, SLA components) were committed under #37 and #40. Code already exists and is deployed. Closing.
Mark 2026-06-08 05:47:58 +00:00
  • closed this issue
  • removed the
    quickfix
         label
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-implement

   
blocked:gate-plan

   
blocked:needs-attention

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:no-procedure

   
blocked:preflight

   
bug

Something is not working correctly

  
feature-request

   
in-progress

   
lint-cleanup

   
needs-decompose

Ready to be decomposed into sub-issues

  
needs-triage

   
ops-task

   
quickfix

   
security/medium

Medium severity security issue

  
triage-approved
No labels
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-implement
blocked:gate-plan
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-procedure
blocked:preflight
bug
feature-request
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-task
quickfix
security/medium
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/msp_c2#39
No description provided.