Email notifications
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
## Description:
- Short Description of the needed Epic in the below format
* As an applicant, ministry coordinator and IAO staff
* I want email notifications
* so that I am aware of updates to a request status or actions that need to be taken
* What are the most critical features being built as part of this Epic
* Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.
----
**Sizing**
* T-shirt size:
[ ] S
[ ] M
[ ] L
[ ] XL
(S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints).
* *Risks and Assumptions**
1. [ ] What are assumptions?
2. [ ] What are the risks?
3. [ ] Have we done an RFC on a technical approach?
4. [ ] Are the dependencies (technical, business, regulatory/policy) known?
5. [ ] Has work on this Epic been prioritized with key stakeholders?
Contributor guide
Research direction
No files, tests, entry points, technical approach, dependencies, or concrete notification requirements are identified. Start by clarifying which request-status updates and required actions need email notifications for each listed role, then define the prioritized scope and acceptance criteria before locating implementation work.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100