Improve reject suggestions

[yfdyh000]

The recent “[AMO]: new titles and descriptions” import brought a lot of fuzzy matches but incorrect translations, and I just saw some issues about rejecting suggestions so post them here.

1. When I approve a translation, the remaining fuzzy translations are not automatically rejected. I understand that this is asking to review them, but the fuzzy matchs is likely to be incorrect for this situation. It should be automatically rejected unless it is fully or highly matched. Or provide an option to automatically reject other translations (including human suggestions), similar to submitting as a suggestion.
2. It is convenient to select multiple strings and “reject all suggestions” button, but I want it to be more flexible if I can reject suggestions for a given range, such as importers only, specific translator. Also, I missed the Select All button in the upper right corner because it is less obvious (far from main view). It would be better if support more ways, such as holding down Shift to select the order, Ctrl+A to select all strings.
3. A glitch, the flag and count of the fuzzy strings list is not updated after I reject all suggestions.
4. Permanently deleting a suggestion is not supported, and sometimes this may be required, such as typing errors. Of course, this brings associated risks. I think permanent hiding (visible only to admin/managers) is an acceptable solution. Hiding by default is also a convenient and highly visible option, which applies to non-abuse suggestions, which is the main case.

[mstanke (Michal Stanke)]

• When I approve a translation, the remaining fuzzy translations are not automatically rejected. I understand that this is asking to review them, but the fuzzy matchs is likely to be incorrect for this situation. It should be automatically rejected unless it is fully or highly matched. Or provide an option to automatically reject other translations (including human suggestions), similar to submitting as a suggestion.

Is that for mass operations, or standard single string operations too?

• It is convenient to select multiple strings and “reject all suggestions” button, but I want it to be more flexible if I can reject suggestions for a given range, such as importers only, specific translator. Also, I missed the Select All button in the upper right corner because it is less obvious (far from main view). It would be better if support more ways, such as holding down Shift to select the order, Ctrl+A to select all strings.

You can filter the string you want to reject using the filters first, and than select them all. I hope it does select the filtered lists, not all strings in the view.

I haven’t found any general bug for mass actions discoverability, but https://bugzilla.mozilla.org/show_bug.cgi?id=1355835 should cover the shortcuts.

• A glitch, the flag and count of the fuzzy strings list is not updated after I reject all suggestions.

Is it https://bugzilla.mozilla.org/show_bug.cgi?id=1477581?

• Permanently deleting a suggestion is not supported, and sometimes this may be required, such as typing errors. Of course, this brings associated risks. I think permanent hiding (visible only to admin/managers) is an acceptable solution. Hiding by default is also a convenient and highly visible option, which applies to non-abuse suggestions, which is the main case.

That sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1397377, which is decided to happen.

[yfdyh000]

Is that for mass operations, or standard single string operations too?

Standard single string operations only.

You can filter the string you want to reject using the filters first, and than select them all. I hope it does select the filtered lists, not all strings in the view.

Yes. In one case, the fuzzy and human suggested strings are coexisting, I have to approve and reject respectively - I can’t reject all suggestions of specific source in bulk.

Is it https://bugzilla.mozilla.org/show_bug.cgi?id=1477581?

Yes.

That sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1397377, which is decided to happen.

Thank you for your response.

[mstanke (Michal Stanke)]

@mathjazz are the first two points something we know about and is already reported to improve? Or is there some reason behind that, why Pontoon does (and should?) behave that way?