users hit stop work instead of submit work after completing hackathon prizes which messes up data collection
Open
gpg - events business
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 776
- PR merge metrics
- No merged PRs in 30d
Description
### Circumstances
When developers start work on a hackathon issue, instead of correctly hitting submit work, they mistakenly hit "stop" work because they assume that's what one is supposed to do after completing the issue.
This messes up the data collected in our DB, and makes it difficult for us to correctly associate work started interest, work submitted, and submission links for our sponsors.
### Description
The correct way to fix this would be to re-think the bounties architecture but a quick fix is to modify our user's behavior with better language positioning.
Suggested:
Start Work
Submit Work
Quit Bounty
Contributor guide
Assessment
This issue has not been assessed yet.