Filtering on untranslated strings produces unexpected results

[Dave Neary]

When listing all of the strings in a project, move to the last page. Filter on untranslated strings. If there are many fewer untranslated than translated strings, you will see "No strings match your request". The position in the list of bugs is saved when filtering - so you are trying to load the next 10 strings after position 500 (for example) which was the last page for all strings, but there are not 500 untranslated strings.

The most intuitive behaviour would be to jump to the first or last page of the untranslated stringswhen applying a filter. First is probably easiest. People who expect that filtering on something, and then going back to "all" will bring them back to the same place will be disappointed. But people who expect to see the filtered results when applying a filter will be happier.

[Carlos Perelló Marín (carlos)]

Sorry, this seems to be a regression. It's supposed to work as you describe.

[Carlos Perelló Marín (carlos)]

Fixed in RF 4483

[Jem (jem-mawson)]

I confirm that this is still an issue at the current time. (Sorry, not sure how to tell if this fix has been released yet).

[Carlos Perelló Marín (carlos)]

Once we set it as 'Fixe released' the patch is on production.

Could you add instructions about how to reproduce the bug?

[Jem (jem-mawson)]

1. Choose a project to translate. It must have at least a few pages of untranslated strings.
2. Set the filter to "Show Untranslated"
3. In this example there are 35 untranslated strings. The summary will say "1->10 of 35 results".
4. Translate this page and click "Save & Continue"
5. Next page loads and the summary will say "11->20 of 25 results"
6. Translate this page and click "Save & Continue"
7. Next page loads and the summary will say "There are no messages that match this filtering." ... Rosetta was most likely attempting to show items "21->30 of 15 results"

[Jem (jem-mawson)]

The attachment shows the result. Note the following:

1. Fltering to show untranslated.
2. Message - "There are no messages that match this filtering."
3. Message - "Translation status: English (Australia) 57%"

[Данило Шеган (danilo)]

Solution is to switch pages based on 'sequence' number: Carlos, can we do that easily while leveraging the batching infrastructure?

[Данило Шеган (danilo)]

Btw, guys, look at bug #63557

[Carlos Perelló Marín (carlos)]

Indeed this problem is bug #63557.

I think the problem is solved just forwarding to the start of the batch if there are not messages for the selected batch slot.

Please, add any new comment to bug #63557.

Cheers.