feat(schedule): tell the admin when editing a past exception doesn't change the frozen day #247

New issue

Open

opened 2026-10-03 08:47:10 +00:00 by gabogg · 0 comments

gabogg commented

2026-10-03 08:47:10 +00:00

Owner

P3 follow-up from PR #178 review pass 4 (spec axis).

Finding

After the r32 fix, editing a past exception's hours updates the exception entry but deliberately leaves the frozen business-day record alone (ADR 0008: the Original Schedule is never corrected). The admin isn't told, so the exception list can show hours that statistics don't use.

Acceptance Criteria

When an edit targets a day that already has a frozen record, the response says the record was not changed and why. The UI shows that notice, localized in es and en.
Or, if the maintainer prefers, the hours fields for past days are read-only in the form.

P3 follow-up from PR #178 review pass 4 (spec axis). ### Finding After the r32 fix, editing a past exception's hours updates the exception entry but deliberately leaves the frozen business-day record alone (ADR 0008: the Original Schedule is never corrected). The admin isn't told, so the exception list can show hours that statistics don't use. ### Acceptance Criteria - When an edit targets a day that already has a frozen record, the response says the record was not changed and why. The UI shows that notice, localized in es and en. - Or, if the maintainer prefers, the hours fields for past days are read-only in the form.

gabogg added this to the Historical passenger-flow backfill milestone

2026-10-03 08:47:10 +00:00

gabogg added the

ready-for-agent

enhancement

labels

2026-10-03 08:47:10 +00:00

gabogg removed this from the Historical passenger-flow backfill milestone

2026-10-03 12:13:37 +00:00

gabogg referenced this issue

2026-10-03 12:21:13 +00:00

docs(agents): milestones hold only what their delivery needs #266