FireWatch: Notification Status for Users
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
FireWatch current accepts start and end dates and status as input parameters, but it is unclear what these parameters do for the user. This task is to review the UX Design and make input parameters more intuitive and self-explanatory.
**Acceptance Criteria**
- [x] Determine if start and end dates are required.
- [ ] Determine how the status field is tied to notifications being sent, putting notifications on hold, or ending/completing the burn so it can be removed from the system.
**Additional context**
- Notifications are sent to users who have opted in to inform them when certain days are in perscription.
Contributor guide
Research direction
Start by reviewing the UX Design and the FireWatch flow that accepts start dates, end dates, and status. Trace how those parameters relate to notifications and burn completion, then confirm the required dates and document a clear status behavior that satisfies the remaining acceptance criterion.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100