What
Planned work should not open an incident. A maintenance window has a title, message, start and end, and the components it covers. While it runs: the public page shows a scheduled-maintenance card, the components show Under maintenance, checks on those components still run but do not open incidents or mail subscribers; when it ends, everything returns to normal and the window is kept in history.
Pieces
- table
maintenances (+ pivot to components), model, migration
- admin screen (list, create/edit, cancel early), audit lines
- public page section + API (
/api/v1/schedules, Cachet-shaped)
CheckRunner: skip incident creation for covered components while a window is active- subscriber mail: one notice when it starts and when it ends (optional, respects the Subscribers switch)
- tests for the muted-check rule
Happy to discuss the data model here before you start; it is the most-asked missing feature.
What
Planned work should not open an incident. A maintenance window has a title, message, start and end, and the components it covers. While it runs: the public page shows a scheduled-maintenance card, the components show Under maintenance, checks on those components still run but do not open incidents or mail subscribers; when it ends, everything returns to normal and the window is kept in history.
Pieces
maintenances(+ pivot to components), model, migration/api/v1/schedules, Cachet-shaped)CheckRunner: skip incident creation for covered components while a window is activeHappy to discuss the data model here before you start; it is the most-asked missing feature.