feat(dashboard): "needs attention" widget for overdue hutch cleaning/playtime #21

Closed
opened 2026-09-11 00:58:10 +01:00 by Hermes · 0 comments
Collaborator

Summary

Surface hutches that are overdue for cleaning or playtime directly on the dashboard. We already log date_cleaned and last_playtime per compartment, but nothing currently flags staleness — a live check found 11/43 compartments not cleaned in 7+ days and 23/43 with no playtime logged in 14+ days, none of which is visible anywhere in the UI today.

Proposal

  • Add a dashboard widget listing hutch compartments where date_cleaned is more than N days old or last_playtime is more than M days old (suggest configurable thresholds, e.g. default 7 days for cleaning, 14 days for playtime — open to discussion on defaults).
  • Sort by most overdue first; link each row to the hutch for quick action.
  • Consider a matching highlight (red/amber) on the hutches list view itself, not just the dashboard.
  • Compartments with date_cleaned/last_playtime of null (never logged) should also surface, distinctly from "overdue".

Open questions

  • Should thresholds be a global setting (admin-editable) or hardcoded to start?
  • Any per-hutch overrides needed, or is a single sanctuary-wide threshold fine?
## Summary Surface hutches that are overdue for cleaning or playtime directly on the dashboard. We already log `date_cleaned` and `last_playtime` per compartment, but nothing currently flags staleness — a live check found 11/43 compartments not cleaned in 7+ days and 23/43 with no playtime logged in 14+ days, none of which is visible anywhere in the UI today. ## Proposal - Add a dashboard widget listing hutch compartments where `date_cleaned` is more than N days old or `last_playtime` is more than M days old (suggest configurable thresholds, e.g. default 7 days for cleaning, 14 days for playtime — open to discussion on defaults). - Sort by most overdue first; link each row to the hutch for quick action. - Consider a matching highlight (red/amber) on the hutches list view itself, not just the dashboard. - Compartments with `date_cleaned`/`last_playtime` of `null` (never logged) should also surface, distinctly from "overdue". ## Open questions - Should thresholds be a global setting (admin-editable) or hardcoded to start? - Any per-hutch overrides needed, or is a single sanctuary-wide threshold fine?
Sign in to join this conversation.
No labels
No milestone
No project
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
cpressland/rabbitdb#21
No description provided.