Created attachment 1039909 [details] history Description of problem: Following translation issues have been found on cloud intelligence->reports->dashboards page. Please refer attached screenshot and TCMS link: https://tcms.engineering.redhat.com/run/247967/#caserun_9995504 1. Click All Dashbords and click on History drop-down menu: History drop-down menu is glayed out but "History" appears in English after placing a cursor on the drop-down menu. (See the screenshot "History".) 2. Click Default Dashboard - click on the top History drop-down menu: "Chart Report" appears in English while other heading names appear in Japanese. (See the screenshot "Chart Report".) 3. Click Defaut Dashboard from the left: All the names of sample dashboards appear in English. (See the screenshot "Sample dashboards".) 4. Click on any group name from the left: Each group page has a title "XXX" の Dashboards. Since there is no singular/plulal distinction in Japanese, "Dashboards" needs to be changed to "ダッシュボード" ("Dashboard"). (See the screenshot "each group page".) 5. Click on any dashboard name and click on the top Configuration drop-down menu: Edit: When a sample widget is deleted, the following warning appears. "One widget の選択が必要です" Since "One widget" does not make sence in Japanese, it should be changed to "1 つのウィジェット". (See the screenshot "One widget".) 6. Click on any dashboard name and click on the top Configuration drop-down menu: Edit: Sample dashboard drop-down menu "Add a Widget" appears in English. (See the screenshot ""Add a Widget"".) Version-Release number of selected component (if applicable): 5.4.0.5.20150605150206_7daa1a8 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1039910 [details] chart report
Created attachment 1039911 [details] sample dashboards
Created attachment 1039912 [details] each group page
Created attachment 1039913 [details] one widget
Created attachment 1039914 [details] add a widget
Fixed in 5.6, moving to ON_QA for verification.
Verified on 5.6.0.10-rc2.1. Could not reproduce reported issue and hence moving the bug 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