Problem
When preparing translation batches for an external agency, users need to avoid sending the same translation work more than once. A current workaround is to tag each batch with the task date, send only translations with that tag, and later search for items without a tag. This works as lightweight task tracking, but it is manual and easy to misuse.
Customer feedback identified a need for a filter answering: “Has this been in a task before?”
The filter needs to be scoped to a specific target language: a key may have been included in a task for one language but not for another.
Proposed solution
Add a filter in the translation/task preparation workflow that can identify whether the selected language’s translation has ever been included in a task, for example:
Has been in a task: No / Never included in a task- optionally the inverse:
Has been in a task: Yes
The filter should use task history rather than tags, and should continue to work when existing tasks or date tags are used.
Acceptance criteria
- A user can filter by a selected target language.
- The filter can return only translations that have never been included in any task for that language.
- Task history is used as the source of truth; the result is not dependent on manually maintained tags.
- A translation included in a task for language A is still considered “never included” for language B.
- The result can be used when creating/preparing a new batch so duplicate work is not sent accidentally.
- Existing task and tag workflows remain backward compatible.
Context
This is a high-priority workflow improvement for teams that send recurring translation batches to external agencies and need a reproducible way to prevent duplicate requests.
Problem
When preparing translation batches for an external agency, users need to avoid sending the same translation work more than once. A current workaround is to tag each batch with the task date, send only translations with that tag, and later search for items without a tag. This works as lightweight task tracking, but it is manual and easy to misuse.
Customer feedback identified a need for a filter answering: “Has this been in a task before?”
The filter needs to be scoped to a specific target language: a key may have been included in a task for one language but not for another.
Proposed solution
Add a filter in the translation/task preparation workflow that can identify whether the selected language’s translation has ever been included in a task, for example:
Has been in a task: No/Never included in a taskHas been in a task: YesThe filter should use task history rather than tags, and should continue to work when existing tasks or date tags are used.
Acceptance criteria
Context
This is a high-priority workflow improvement for teams that send recurring translation batches to external agencies and need a reproducible way to prevent duplicate requests.