Description of problem: Many filter group names are not translated. For example on Secrets, Pipelines, PipelineRuns, and many others when searched for `filterGroupName: ` in our code. Version-Release number of selected component (if applicable): 4.9+ How reproducible: Always Steps to Reproduce: 1. Open the secret list 2. Open the user settings in another tab, switch the language 3. Reload tab one and open the filter dropdown Actual results: The filter group name like "Status" or "Type" is not translated. Expected results: The filter group name should be translated. Expect that there is no match for `filterGroupName: '` in our code after this was fixed. At the moment I found 17 not translated strings. This does NOT mean that we need also to translate the values (in this ticket), because we normally do NOT translate resource values and the filter item matches them in many cases.
Created attachment 1875011 [details] secret.png
Created attachment 1875012 [details] pipeline.png
Created attachment 1875013 [details] pipelinerun.png
Sorry, I could not verify this on a nightly build. 1. "Type" and "Status" in the filter dropdown are not translated. Please search for `filterGroupName: '` 2. The Pipeline filter shows 0 in translated languages (like Japanese) 3. Just a small nit: The map function is not required here, you can just use secretTypeFilterValues items: secretTypeFilterValues.map((filterValue) => ({
Verified on 4.12.0-0.nightly-2022-07-25-122035
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069