ASA Go: Notifications Epic
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *ASA Go user* **I want** *notifications* **So That** *(Value, why is this wanted, what is the user trying to accomplish)*
**Additional Context**
- https://firebase.google.com/docs/cloud-messaging/manage-tokens
- Spike: https://github.com/bcgov/wps/issues/2848
**Acceptance Criteria**
- [x] #4894
- [x] #4906
- [x] Create DEV Notifications using TEST data
- [x] #5166
- [x] #5165
- [x] #5185
- [ ] Maybe - Track who has actually received a notification (Read Receipt) OR User opened the app in the AM (Self Serve)
**Notes**
[ ] Logic not to Re-issue a Notification if things are the same
[ ] Issue a Notification if things have changed from both Warning to Advisory and Vice Versa
[ ] Change has happened in a Zone you're subscribed to
Contributor guide
Research direction
Review the open acceptance criterion and Notes, then read the Firebase Cloud Messaging token documentation and the spike in #2848. Trace the referenced issues to determine what notification work is complete and define whether the remaining read receipt, self-serve, de-duplication, and warning/advisory behavior is still required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100