-
Bug
-
Resolution: Fixed
-
None
-
High
-
Auto-QA: user is allowed to finish the task if tag errors are absent if they are configured to be
-
Emptyshow more show less
Problem
When runtimeOptions.segments.userCanIgnoreTagValidation is allowed, the user may save segments with tag errors. However, the AutoQA detects and lists the error. Even though "must be zero qualities" is set for tag errors, the user is able to finish the task:

PMs
Same basically must be for PMs: When a PM changes currently a job status to finished, the "must be zero errors" is not respected.
Solution
Each config should do what it says: allow tag errors (userCanIngoreTagValidation) is the permission to save segments with errors. But if tag errors must be zero, then the user must not be allowed to finish the task.
The check must be respected and a warning given, when there are errors:
Normal User:
DE: Einige Pflichtkriterien der AutoQA weisen noch Fehler auf.
EN: Some mandatory criteria of the AutoQA still have errors.
Technical thoughts:
- PM can finish via Job Manipulation (TaskUserassocController)
- User (and PM assigned to task) can finish only via Editor / TaskOverview (TaskController)
- is duplicated by
-
TRANSLATE-5018 status change to finish must respect zero errors config
- Done
- relates to
-
TRANSLATE-3710 Introduce new processing status "draft" for segments
- Done