Problem

Evaluation how good quality estimation works is only really possible, if you can get the KPIs of average post-editing time and levenshtein distance for all segments within a certain TQE value range for a filter set of tasks.

So as an example: Users will want to know, how the average Levenshtein distance and post-editing time was for 

• all segments with a TQE between 90 and 100
• with source language DE and target language IT
• ordered between 25th of December 2025 and 30st of January 2026
• post-edited by user Max Mustermann (so segments edited by Uli Müller would not be taken into account, even if they are from the same tasks as those of Max)
• pre-translated with a GPT 4.1 language resource named "super duper GPT" (so segments pre-translated by TM or a DeepL language resource named "greatest MT on earth" in the same tasks would not be taken into account)

The above criteria would be set as AND filters in the task overview

Solution

Add a filter for the TQE column to the adavanced filters of the task grid analogous to the one that exists for the match rate.

• be careful: There might be segments/tasks without values
• filter should find all tasks with values somewhere in the given range
• KPI window should then calculate the  Levensthein and post-editing time values only
  based on the segments within the range that exist in all tasks that match the current filter set (so all other set filters taken into account)
• Add the KPIs also to the meta data Excel download