Closed michellexing closed 5 years ago
What about bonus? What about ability to return? What about logic conflict with custom vars in tasks/surveys/final survey ?
Actually, 'real kick' is not an option - because of structure and etc. But we can hide and block this user.
How I see it: without bonus, block ability to return, block all actions, hide user in chat and final survey, show user in task/survey text.
That sounds good. Basically users should not be able to come back if they are gone for an entire round, and the way you described it sounds like that would have the same effect.
The user should be shown in the final survey for rounds in which they were present, but not for rounds after they left.
To clarify: 'one full round where a participant has been inactive' - without messages or without messages & survey results ?
Just messages is enough.
Basic version is in dev, you can try it
Thanks — if its working in your tests, we probably can just move it to prod.
I can imagine situation with 1 user in round team. It will be strange. How about this solution?
I imagine we would stop the batch in that situation.
Done, and I added new rule for batch stop: if user is afk, we don't pay bonus.
Currently, we have some users that don't show up for multiple rounds and they are shown as "inactive" to the other users.
INSTEAD WE WANT: After one full round where a participant has been inactive, just kick them out of the task.