Duplicate Submission Verification for Missing Transaction Form
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 776
- PR merge metrics
- No merged PRs in 30d
Description
**User Story:**
As a cgrants user with missing transaction
I want to be blocked from submitting the missing transaction form multiples times
So that I do not end up with confusing notifications duplicates of missing transactions.
**Acceptance Criteria**
details here: https://discord.com/channels/562828676480237578/1024291324058419240/1024651338409328750
**XD Links:**
**Tech Details:**
**Open Questions:**
**Notes/Assumptions:**
Contributor guide
Research direction
Start by reading the acceptance criteria in the linked Discord thread, then trace the existing missing transaction form submission flow in the repository. The issue does not name files, tests, or technical details. Done means preventing repeated submissions and avoiding duplicate missing-transaction notifications as defined by the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100