Skip to content

feat(notifications): Notification priority & grouping system (#122)#273

Open
dagangtj wants to merge 1 commit intorohitdash08:mainfrom
dagangtj:feat/notification-priority-122
Open

feat(notifications): Notification priority & grouping system (#122)#273
dagangtj wants to merge 1 commit intorohitdash08:mainfrom
dagangtj:feat/notification-priority-122

Conversation

@dagangtj
Copy link

Summary

Group and prioritize alerts for clarity, reducing notification fatigue.

Closes #122

Changes

  • Notification service: packages/backend/app/services/notifications.py

    • 5 priority levels: critical, high, medium, low, info
    • 6 groups: bills, expenses, budget, security, insights, system
    • 14 event-to-priority rules (auto-classification)
    • Group collapse when >5 notifications
    • Mark read/dismiss, user preferences
    • Summary with unread counts by priority
  • API: packages/backend/app/routes/notifications.py

    • GET /notifications/ — list with filters (unread, group, priority)
    • POST /notifications/ — create notification
    • GET /notifications/grouped — grouped view with collapse
    • GET /notifications/summary — unread counts
    • POST /notifications/<id>/read — mark read
    • POST /notifications/read-all — mark all read
  • Tests: 22 test cases

Acceptance Criteria

  • Production ready implementation
  • Includes tests (22 cases)
  • Follows existing code patterns

…sh08#122)

- 5 priority levels: critical, high, medium, low, info
- 6 notification groups: bills, expenses, budget, security, insights, system
- Auto-priority from event type (14 event rules)
- Group collapse when >5 notifications
- Mark read/dismiss, user preferences
- REST API: CRUD, grouped view, summary, mark-all-read
- 22 test cases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Notification priority & grouping system

1 participant