Bug 1007167

Summary:

[ja-JP][SAM Web GUI] Save button not found in editing an existing role

Product:

[Retired] Subscription Asset Manager

Reporter:

Aiko <asasaki>

Component:

katello

Assignee:

Katello Bug Bin <katello-bugs>

Status:

CLOSED WONTFIX

QA Contact:

SAM QE List <sam-qe-list>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

1.3

CC:

asasaki, qe-i18n-bugs, tomckay

Target Milestone:

Keywords:

i18n

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2013-12-02 20:46:04 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Bug Depends On:

Bug Blocks:

971511

Attachments:

Description	Flags
Save button found	none

Description Aiko 2013-09-12 04:27:09 UTC

Filed from caserun (INSERT URL HERE)

Version-Release number of selected component (if applicable):
SAM-1.3.0-RHEL-6-20130829.1

Steps to Reproduce: 
Depending on user's permissions, hover the mouse over the available tabs and
submenu as well as upper right links (i.e. Notifications count, Logout link,
etc)


1. Click on the name of the required role from the left NAME panel.
2. Click the Edit Role Details button at the bottom of the window. 
3. Click on the details to edit.

 


Actual results: 
#FIXME
The Save button does not appear.

Expected results:
The button should appear to save the editite details.

Comment 1 Tom McKay 2013-09-12 11:48:44 UTC

There is no "Save" button shown on that page until until one of the two fields themselves are selected (Name or Description). 

Please provide screenshot of what you are seeing.

Thanks!

Comment 2 Aiko 2013-09-13 00:20:03 UTC

Created attachment 797063 [details]
Save button found

Comment 3 Bryan Kearney 2013-12-02 20:46:04 UTC

The move to Foreman and the new UI invalidates all previous localization testing. We will need to do a full pass through the UI again.