Data migration from existing bounty types
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 776
- PR merge metrics
- No merged PRs in 30d
Description
**User Story:**
As a contributor
I want the bounty explorer to reflect the new naming conventions holistically
So that there is consistency with what im looking at/for
**Acceptance Criteria**
GIVEN I have bounties that fit the exisiting bounty types - Traditional, Cooperative, or competition
WHEN i deploy the new bounty creation workflow that includes the trimmed down bounty type list
THEN any existing bounties that = Cooperative or competion should reflect "Multiple"
AND this should reflect on the bounty explorer filters
**Notes:**
We will need to run this on deployment
Contributor guide
Research direction
Start by locating where bounty types are stored and migrated during deployment, then trace the bounty explorer filters that consume those values. Done means existing Cooperative and competition bounties are represented as "Multiple" after deployment and the explorer filters reflect the renamed type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100