Bug 697016

Summary:	Add a mechanism to reset limits to unlimited [RFE]
Product:	Red Hat Enterprise MRG	Reporter:	Trevor McKay <tmckay>
Component:	cumin	Assignee:	Chad Roberts <croberts>
Status:	CLOSED ERRATA	QA Contact:	Jan Sarenik <jsarenik>
Severity:	low	Docs Contact:
Priority:	low
Version:	Development	CC:	jsarenik, ltoscano, matt, sgraf
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:	In the limit editing form, there was no intuitive way of setting the limit to the "unlimited" value. This update adds a button, which changes the text book entry to "Unlimited". Alternatively, the user can also type the value "unlimited".	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-07 16:44:32 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 Trevor McKay 2011-04-15 15:41:12 UTC

Tracker BZ for future work.

Currently any limit value over 1,000,000 displays as "unlimited" in cumin (this is somewhat arbitrary, but in condor unlimited is just a really big number).  

  In a UI review the question was asked "How does a user set a value back to 'unlimited' if it has been set below the threshold?"

  It would be nice to have a button, or a checkbox, or some mechanism to set the value back to unlimited.  Perhaps allowing the input box to accept "unlimited" or a number as valid entries, and an "unlimited" button that puts the text "unlimited" in the box?

Comment 1 Chad Roberts 2011-05-12 14:25:28 UTC

Available in revision 4761

I have added a new button to the form.  When clicked, it will update the text in the box to read "Unlimited" (of course, the user could still type in the value which would also be acceptable...case does not matter).  

The previous behavior of treating any value over 1,000,000 as "unlimited" still exists.  The purpose of this BZ was to give the user an option that was more obvious to get their limit set to unlimited.

Comment 2 Chad Roberts 2011-05-12 14:25:28 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:
Cause:  The limit editing form had no good/obvious way to get the limit set to unlimited.

Consequence:  The user would be presented with a confusing situation, being unsure of how to get their limit set back to unlimited.

Fix:  We have included a new button that will change the text box entry to "Unlimited"...the user could also just type in the value "unlimited" and that would work as well.  When the user submits the form, the limit becomes "Unlimited".

Result:  The Limit editing form now has a less-confusing mechanism to get the limit set to "Unlimited".

Comment 3 Chad Roberts 2011-06-01 20:34:12 UTC

Per the latest UI review, we are going remove the "unlimited" button in favor of an "unlimited" checkbox that, upon checking, will make the input box read-only and set the contents to "Unlimited".  Upon unchecking the box, the input box will become writable again.

Comment 4 Chad Roberts 2011-06-01 21:23:31 UTC

Updated fix in revision 4796.

Comment 5 Jan Sarenik 2011-06-21 15:01:11 UTC

Verified in cumin-0.1.4840-1.el6.noarch

Comment 6 Eva Kopalova 2011-08-09 14:42:16 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,7 +1 @@
-Cause:  The limit editing form had no good/obvious way to get the limit set to unlimited.
+In the limit editing form, there was no intuitive way of setting the limit to the "unlimited" value. This update adds a button, which changes the text book entry to "Unlimited". Alternatively, the user can also type the value "unlimited".-
-Consequence:  The user would be presented with a confusing situation, being unsure of how to get their limit set back to unlimited.
-
-Fix:  We have included a new button that will change the text box entry to "Unlimited"...the user could also just type in the value "unlimited" and that would work as well.  When the user submits the form, the limit becomes "Unlimited".
-
-Result:  The Limit editing form now has a less-confusing mechanism to get the limit set to "Unlimited".

Comment 7 errata-xmlrpc 2011-09-07 16:44:32 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