Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 859415 - Simple org creation not usable
Simple org creation not usable
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI (Show other bugs)
6.0.1
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: Unused
Assigned To: Brad Buckingham
Og Maciel
: Triaged
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-09-21 09:43 EDT by Jeff Weiss
Modified: 2014-11-09 17:52 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The "Save" button was disabled when creating a new Organization. This fix enables the save button and auto-generates a label if the user clicks "Save" without specifying a label. The "Save" button is now enabled.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-12-04 14:56:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-04 19:39:57 EST

  None (edit)
Description Jeff Weiss 2012-09-21 09:43:07 EDT 
Description of problem:


Version-Release number of selected component (if applicable):
Katello Version: 1.1.12-1.git.188.8955f22.el6_3 

How reproducible:


Steps to Reproduce:
1. Go to orgs, click New Organization
2. Fill in a name "foo"
3.
  
Actual results:
now what?  Save button is disabled, user has no clue why or what to do next

Expected results:
Save button is enabled.

Additional info:
The purpose of this appears to be to autogenerate a label.  The app cannot wait for the focus to change to do this, it has to be a keypress event or something "sooner" than waiting for the user to be confused and click somewhere else.
Comment 2 Brad Buckingham 2012-09-26 13:56:13 EDT 
In order to resolve this one, we'll enable the save button and auto-generate a label if the user clicks save without a labeling having been specified.  In the success notice, we'll include text similar to:

Organization abc created.  Note: Since a label was not been provided, a label of 'abc' has been automatically assigned.  If you would like a different label, please delete the organization and recreate it with the desired label.
Comment 3 Brad Buckingham 2012-09-28 10:04:59 EDT 
katello github pull request: 
https://github.com/Katello/katello/pull/759

katello github commit:
4d860bf8187600f3e9196b6d1fceefe2348a9788
Comment 6 Og Maciel 2012-10-02 18:10:24 EDT 
@Brad: the save button was enabled before I even typed any values into the form. Is this the designed behavior?

I saw two distinct behaviors while verifying this:

1. I created organization Bar with default environment DEV. When I clicked the save button I got the following notifications:
* "Organization 'Bar' was created." [GREEN in color]
* "A label was not provided during environment creation; therefore, a label of 'DEV' was automatically assigned. If you would like a different label, please delete the environment and recreate it with the desired label." [GREY in color]

2. I created the Foo organization but did not provide a default environment.  When I clicked the save button I got the following notifications:
* "Organization 'Foo' was created." [GREEN in color]
* "Click on 'Add Environment' to create the first environment " [GREY in color]

Though it seems that behavior (1) does follow the explanation from comment #2, imo it does not match the expected behavior for (2).

I'll be perfectly fine with filing a separate BZ and ask for (2) to also display the same message as (1) informing of the default label that was created, just for standardization of the web ui experience. I will wait for your comment/suggestion before closing this.
Comment 7 Og Maciel 2012-10-02 18:25:34 EDT 
Verified using:

* candlepin-0.7.8-1.el6cf.noarch
* candlepin-selinux-0.7.8-1.el6cf.noarch
* candlepin-tomcat6-0.7.8-1.el6cf.noarch
* katello-1.1.12-12.el6cf.noarch
* katello-all-1.1.12-12.el6cf.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.8-1.el6cf.noarch
* katello-cli-1.1.8-6.el6cf.noarch
* katello-cli-common-1.1.8-6.el6cf.noarch
* katello-common-1.1.12-12.el6cf.noarch
* katello-configure-1.1.9-6.el6cf.noarch
* katello-glue-candlepin-1.1.12-12.el6cf.noarch
* katello-glue-pulp-1.1.12-12.el6cf.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.1.1-1.el6cf.noarch
* pulp-1.1.12-1.el6cf.noarch
* pulp-common-1.1.12-1.el6cf.noarch
* pulp-selinux-server-1.1.12-1.el6cf.noarch
Comment 9 errata-xmlrpc 2012-12-04 14:56:15 EST 
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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Comment 10 Mike McCune 2013-08-16 14:15:26 EDT 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.