-
-
Notifications
You must be signed in to change notification settings - Fork 283
Description
Is your feature request related to a problem? Please describe.
Tasks are not created equal, and their difficulty, or effort required to complete may not be homogeneous in any given project.
It's always more difficult to deal with existing data and requires understanding of how to do so in the first place. More complex task histories make it more difficult to provide feedback. Those who did not submit a/the task are even less likely to recieve any.
Describe the solution you'd like
Set a default filter and sort by in the task selection panel (contribute page) to "available for mapping and least recently updated" for at least beginers, if there is a task available for mapping. This would reduce the likelihood that they would choose a task with lots of existing data which requires dealing with.
Perhaps the automatic select a task could prefer the selection of such 'no history' tasks for beginers if they don't use the task selection panel.
If the only user to lock a task previously split it then this could be counted as 1-1=0 or similar for the puropses of task selection, as contributors must currently lock a task if they wish to split it in a published project.
Describe alternatives you've considered
Cross-referencing the backgorund map when selecting tasks, or viewing the changesets via task data before selecting a task. However this can require an explanation of how to do, so I'd prefer the TM to guide the beginer contributors instead.
Additional context
This may also address #4784