Not Considering

Ignored messages will not be retriggered - that is the whole point of this feature. If you require full scan and absolutely no messages, please instruct your translators/reviewers to not use this feature. 

Enable QA check workflow step to fully rescan the task

We thought the QA check workflow step fully rescanned the task to ensure that anything ignored would be reset as an issue to validate by our team. Recently we found out that the QA check step only rechecks what is not ignored and anything ignored does not make it to our team to validate. With how easy it is to ignore all issues, we need the ability to have the QA check step recheck everything. This also enables this team to see common false positives to update QA rules or open support tickets due to bugs. We have no insight with how the step works as it is.

Russell Banton

  • I also see that this cannot be voted on anymore as well.

  • Speaking with some other enterprise customers of TE, there are others that see this need. If we were working directly with linguists, it would be one thing to try and direct them how they should use ignore. Since we work with vendors and they work with SLVs and MLVs, the supply chain can sometimes become quite deep. We are not able to confirm all information flows properly to all vendors, sub-vendors, and linguists. We have real issues now where we have not been able to have the tasks fully revalidated with the QA checks and this has led to issues in published content.

    We truly need the ability to work at an enterprise level for how QA can be managed.

  • I will also add that the proposed workaround is to manually open the task in the Online Editor and restore them. This is not scalable and even once the Online Editor supports opening multiple tasks at once, this is still not scalable as you will have to open every project even if there are no issues.