start work without accepting the job?
Has something changed in the workflow? We've recently seen examples where users are able to start work (e.g., make edits to segments that are saved) without accepting the job (e.g., status remains at Not Started). It's important that we track when each user begins and completes each job, so we need to make sure that no one can start work before accepting the job.
0
-
As a follow-up to this, it's unclear from the access rights how to restrict a user from working on a job (accessing the TUI editor window) until s/he has accepted a job. Any ideas?
0 -
We have had this issue come up a few times as well, randomly. I am interested to see if there is any resolution to this one!
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
2 commentaires