Temporary location snooze / mute #82
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#82
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
"Mute home for 3 days while I travel," or "snooze this active advisory for 1 hour." The current model is binary always-on per subscription; a time-boxed mute is a common real need. Missed because the mental model was continuous monitoring. Effort S, value Medium.
Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding I-12.Done in #102 (merged).
Location.snoozed_until(migration 0022): while set to a future time, a location's alerts still record the dashboard history row but channel dispatch is suppressed; a past value = not snoozed (auto-expires, no cleanup job).POST /api/locations/{id}/snooze(duration or explicituntil) and/unsnooze, can-manage-location + CSRF, with a snooze control + "🔕 Snoozed" badge in the locations UI.snoozed_untilis now inLocationRead.