Bug 1398170 - [ja_JP] Red Hat Insights - Splash - 'Automate Your Response' section is not translated
Summary: [ja_JP] Red Hat Insights - Splash - 'Automate Your Response' section is not t...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Hybrid Cloud Console (console.redhat.com)
Classification: Red Hat
Component: [Legacy] Insights Web UI
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jaylin Zhou
QA Contact: Krishna Babu K
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 09:22 UTC by Krishna Babu K
Modified: 2017-03-06 23:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-06 23:31:18 UTC
Target Upstream Version:


Attachments (Terms of Use)
Screen shot reference for the reported issue. (494.79 KB, image/png)
2016-11-24 09:22 UTC, Krishna Babu K
no flags Details

Description Krishna Babu K 2016-11-24 09:22:02 UTC
Created attachment 1223661 [details]
Screen shot reference for the reported issue.

Description of problem:
Splash page has 'Automate Your Response' section untranslated.

Version-Release number of selected component (if applicable):
Insightsbeta

How reproducible:
Always

Steps to Reproduce:
1. Log into https://access.redhat.com/insightsbeta/splash/ with ja_JP locale
2. Scroll page to 'Automate Your Response' section, if this is not an image then the content should get translated.


Actual results:
Translation not available

Expected results:
If missing translation part is not an image then the content should get translated.

Additional info:
Reference screen shot attached

Comment 1 Jozef Hartinger 2016-12-02 08:30:13 UTC
Missing translation keys were added in master http://labs-git.usersys.redhat.com/labs/insights/commit/e1826628267272e08fecf7c6ea27feb8969620e8

Comment 2 Krishna Babu K 2017-01-13 10:23:35 UTC
Verified on https://access.redhat.com/insightsbeta/splash/ , can not reproduce now.


Note You need to log in before you can comment on or make changes to this bug.