Bug 712974

Summary:	[RFE]Limits table: Make the value the hyperlinked value rather than the name
Product:	Red Hat Enterprise MRG	Reporter:	Chad Roberts <croberts>
Component:	cumin	Assignee:	Chad Roberts <croberts>
Status:	CLOSED ERRATA	QA Contact:	Jan Sarenik <jsarenik>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0	CC:	jsarenik, ltoscano, matt, tmckay
Target Milestone:	2.0.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cumin-0.1.4840-1	Doc Type:	Bug Fix
Doc Text:	The limits-editing page did not follow the convention of hyperlinking the text of the object to be edited, which may have been confusing. This update ensures that the limit value is hyperlinked instead of the limit name, thus ensuring consistency with other editing pages.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-07 16:44:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	723887

Description Chad Roberts 2011-06-13 19:16:28 UTC

In order to be consistent with the quotas table, the hyperlinked column of the table should be the value column.  The thought here is that the user should be clicking the value that they will be editing rather than the name of the value to be edited.


Steps to Reproduce:
1.  Go to the Limits table.
2.  Note which column is hyperlinked
  
Actual results:  The name column is currently hpyerlinked


Expected results:  The "Max allowance" column should be hyperlinked (link goes to limit edit form).

Comment 1 Chad Roberts 2011-06-13 19:39:12 UTC

This is in as of revision 4810.

Comment 3 Jan Sarenik 2011-07-22 12:18:36 UTC

Verified with cumin-0.1.4878-1.el5

Comment 4 Chad Roberts 2011-07-25 15:18:17 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C:  The limits editing page did not follow the usual flow of having the hyperlinked text be the object that was going to be edited.
C:  Linking the limit name rather than the limit value may have been confusing since it is actually the value that you will be editing, not the name.
F:  Change the hyperlinked column from name to value
R:  The page now conforms to the usual cumin flow.

Comment 5 Douglas Silas 2011-08-08 14:11:20 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1 @@
-C:  The limits editing page did not follow the usual flow of having the hyperlinked text be the object that was going to be edited.
+The limits-editing page did not follow the convention of hyperlinking the text of the object to be edited, which may have been confusing. This update ensures that the limit value is hyperlinked instead of the limit name, thus ensuring consistency with other editing pages.-C:  Linking the limit name rather than the limit value may have been confusing since it is actually the value that you will be editing, not the name.
-F:  Change the hyperlinked column from name to value
-R:  The page now conforms to the usual cumin flow.

Comment 6 errata-xmlrpc 2011-09-07 16:44:43 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-1249.html