Contact an Applicant
- 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 a FOI Analyst
* I want to contact an applicant
* so that I can communicate the status of their request
* or clarify information needed
* 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, or entry points are named in the issue. Start by clarifying the applicant-contact workflow, expected features, dependencies, risks, and technical approach with project stakeholders. Done cannot be defined until the epic is scoped and its acceptance criteria are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100