RFE: Allow priorities to take into account how near tasks are to currently edited tasks
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
Research direction
No files or tests are named. Start by locating how task priorities and currently edited tasks are represented, then clarify whether the desired outcome is radius-based locking or priority changes; done should include an agreed behavior and tests for the distance thresholds.
Written by the indexing model from the issue text.
Description
I want to avoid editor conflicts since, in my experience, an editor will often make a mistake during conflict resolution.
So I'd like to either have a way to "lock" tasks within a certain radius of a task currently being mapped or a way to de-prioritize those tasks (e.g., if no editor working on task within 5 km, then task is high priority, else if editor is working on a task within 5 km but more than 3 km away, then task is medium priority, else if editor is working on a task less than 3 km away, then task is low priority).
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from maproulette/maproulette-backend
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
maproulette/maproulette-backend#1087 ·
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
maproulette/maproulette-backend#1289 ·
-
Auth for scripts and CI after API key removal (personal access tokens) – tracking and use casesOpen
Difficulty 5/5 Over a week Newbie friendliness 8/100
maproulette/maproulette-backend#1288 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
maproulette/maproulette-backend#1258 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
maproulette/maproulette-backend#1198 ·
All issues in maproulette/maproulette-backend
Similar issues
-
Module: Form Builder
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
orbeon/orbeon-forms#7943 ·
Maintainers usually reply within 2 days
-
module: core
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
bigbluebutton/bigbluebutton#26028 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaworks/zio-elasticsearch#869 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Philippus/sbt-dotenv#355 ·
-
LFSR.tapsMaxPeriod: 17 second tap sets (widths 725 to 755) are a single number larger than the widthOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
chipsalliance/chisel#5512 ·
Maintainers usually reply within 2 days