CodeForPhilly / CodeForPhilly/stately
"Awaiting" shows cases that are "approved" or "rejected" if submitter was notified
- Dominant language
- Python
- Stars
- 22
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Travel request currently sends an email to the submitter when a case is approved or rejected. As a result, the submitter is "assigned" to the case in the "Approved" or "Rejected" state, so it shows up in the `/awaiting` endpoint. I think the resolution is for that query to exclude cases whose states have no actions.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the implementation of the `/awaiting` endpoint and its case query. Inspect how case states expose available actions, using the approved and rejected notification flow described in the issue. Done means cases with no actions are excluded while actionable assigned cases still appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100