maproulette / maproulette/maproulette-backend
Default priority not cloned
Open
Nobody has claimed this yet.
admin
quick-fix
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
When cloning a challenge, the default priority is not cloned but set to the default "High".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Inspect the challenge-cloning path and compare how the default priority is read and assigned; add or update a focused test showing that a cloned challenge preserves its source priority rather than replacing it with High.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100