Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability for mappers to remap and change the state of a task after completion #786

Open
nathanopen opened this issue May 13, 2020 · 1 comment

Comments

@nathanopen
Copy link

Can we add the ability to remap and change the state of a task after they have already marked it as complete (be it in any state). The use cases mostly come from the QC process, but may also come from self-learning.

Some examples of when this may be useful.

For “I fixed it”: An example would be it a user was making edits based on an incorrect understanding of policy, so if a user added 100 street names based on what they thought was an approved resources, but it is discovered it is not an approved resources, they edits would need to be reverted and the tasks changed to “too hard/can’t see”, if no other ground truth were available.

For “too hard/can’t see” the opposite of the above may be true, the mapper was marking tasks as can’t see, but there was an approved resource they could use, and didn’t know about, so they can go back and add the names to streets and change the tasks to “I fixed it”

For “not an issue”, this too may come from a misunderstanding of policy, the mapper may think there is not an issue, but there really is, so in keeping with street names, a new mapper might see that a street name is “Main St” and it is being flagged as needing fixed, and they may not know that the street type needs to be spelled out and not abbreviated, so they will mark they task as “not an issue”, but then discover that street names need to be full spelled out and has to go back and fix the names and mark the tasks as “I fixed it”

@nrotstan
Copy link
Contributor

This is possible through the Task Review process. Reviewers can reject tasks, and mappers can then go back and update them. Alternatively, reviewers can change the status themselves (or even apply a fix and mark the task as "approved with fixes").

Mappers can choose to have their tasks reviewed on an individual basis, but can also opt in to having all of their tasks automatically queued for review (in their User Settings). If you're running your own server, you can also force all tasks go through review and not have to worry about users opting in.

The review system also provides a way for mappers to see their tasks that require revisions, which can otherwise be difficult for mappers to discover, and sends in-app notifications (and optionally emails based on the mapper's settings) to mappers when their tasks are reviewed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants