fix(item): keep list entries out of the notification stream #284
No reviewers
Labels
No labels
adr
android
area/calendar
area/design-system
area/i18n
area/jobs
area/offline
area/server
area/testing
bug
ci
duplicate
enhancement
help wanted
invalid
notifications
question
reliability
security
severity/low
severity/medium
tracking
web
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
eagraiclainne/app!284
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/list-quiet-notifications"
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?
Fixes #281.
Ticking a list entry rang the family's JOB_COMPLETED bell as if a chore had been done. Create and AssignUser already keep list entries quiet. CompleteItem was the one announcement without the standalone guard, and the due-reminder ticker would ring for a list entry that carried a deadline.
Both now check for a list ref, so lists and their entries send nothing. Specs cover the three cases: a standalone job still announces, a list entry stays silent, a dated list entry does not ring.
Server-only change. No client surface sends these, so parity holds.
🤖 Generated with Claude Code
1e1af1a278fc396db762Test report
Coverage: 27.0%
Updated by the check workflow · commit
fc396db762