Description of problem:On cloud intelligence->Reports page, strings in the left pane need to be translated. Please refer attached screenshot. Also refer LM's comments from following link: https://tcms.engineering.redhat.com/run/247967/#caserun_9995501 Version-Release number of selected component (if applicable): 5.4.0.5.20150605150206_7daa1a8 How reproducible: always Steps to Reproduce: 1.login with ja_JP locale 2. go to cloud intelligence->reports 3. observe the strings on the left pane. Actual results: strings are not translated Expected results: strings should be translated. Additional info:
Created attachment 1039364 [details] reports pane
I'm combining all the translations issues on the Cloud intelligence->reports page here in order to make it better for overall defect management. It will be helpful for future check-ins as well as defect verification further. Updating the bug summary accordingly. Following issues have been observed for translations on Cloud intelligence->reports page: 1. All strings on the left pane appear in English. (See the screenshot "Reports") 2. Click Saved Reports from left panel: Strings on the right panel all appear in English. (See the screenshot "Reports on right panel") 3. Click Saved Reports from left panel: All strings on the top drop-down menu appear in English. (See the screenshot "Top drop-down menu.") 4. Click Saved Reports from left panel-Delete: An error message after selecting "Delete", "★No Reports available." appears in English. (See the screenshot "No Reports available.") 5. top Download icon button: The button name "Download" appears in English. (See the screenshot "Download".)
Created attachment 1039828 [details] reports on right panel
Created attachment 1039829 [details] top down
Created attachment 1039831 [details] top down drop menu
Created attachment 1039832 [details] no reports available
Created attachment 1039833 [details] download
Fixed in 5.6, moving to ON_QA for verification.
Verified on 5.6.0.10-rc2.1. All translations are available now. Moving it to Verified as of now.
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, 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/RHBA-2016:1348