-
Bug
-
Resolution: Fixed
-
None
-
Medium
-
The PM is allowed to set the Job associations as they want it. This may lead to an inconsistent workflow. One error when editing segments in an inconsistent workflow is fixed now.
-
Emptyshow more show less
Problem
The PM are very mighty and can set the Job associations as they want it. The disadvantage is that this may lead to an inconsistent workflow. For example: If a task in workflow step second review with a second reviewer in status open gets an additional user with the role translator and status open, this leads in an inconsistent workflow. Since translator and second reviewer may not have state open at the same time.
Normally the workflow should remain in the step of the first added user.
If then the second user tries to save a segment, he gets the TaskUserAssoc Entity Not Found error:
[TRANSLATE-2259] Inconsistent workflow may lead in TaskUserAssoc Entity Not Found error when saving a segment.
| Start Date [Gantt] | New: 23/Apr/24 5:00 AM |
| Status | Original: Final pull request made [ 10005 ] | New: Done [ 10000 ] |
| Workflow | Original: MittagQI Workflow [ 30129 ] | New: MittagQI Workflow with Peer [ 36455 ] |
| Fix Version/s | New: translate5 - 5.0.11 [ 11501 ] |
| ChangeLog Description | New: The PM is allowed to set the Job associations as they want it. This may lead to an inconsistent workflow. One error when editing segments in an inconsistent workflow is fixed now. | |
| Summary | Original: Inkonsistent workflow may lead in TaskUserAssoc Entity Not Found error when saving a segment. | New: Inconsistent workflow may lead in TaskUserAssoc Entity Not Found error when saving a segment. |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |
| Status | Original: Selected for Development [ 10100 ] | New: In Progress [ 3 ] |
| Status | Original: Open [ 10002 ] | New: Selected for Development [ 10100 ] |
| Link | New: This issue causes TS-603 [ TS-603 ] |