Request revalidation sets the task status to validated instead of mapped

[ramyaragupathy]

Sometimes, instead of setting the task status as mapped, Request revalidation action updates the task history table with validated state - we have encountered this thrice so far.

[willemarcel]

Proposal: instead of creating a new MAPPED task history item, delete all VALIDATED history items. It would also solve the problem validators have because they can not validate a task they asked revalidation.

[aawiseman]

I think this sounds useful!

[wireguy]

When a validator chooses 'request revalidation', they are locked out of working on that task. TM thinks that validator mapped the task and is requesting validation, and we can not validate tasks we map. They need to find another validator and get them to move the task back to 'needs more mapping'

Maybe tm should go back to knowing who the mapper was that said the task was complete and ready for validation.