Bug 744828

Summary: Admin UI - Catalog Entry creation expects the user to choose a catalog, when the user has already selected a Catalog
Product: [Retired] CloudForms Cloud Engine Reporter: chris alfonso <calfonso>
Component: aeolus-conductorAssignee: chris alfonso <calfonso>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, dajohnso, deltacloud-maint, dgao, hbrock, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:15:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description chris alfonso 2011-10-10 15:24:09 UTC 
Description of problem:
When creating a catalog entry in the admin ui, the user navigates to the catalog entry creation screen from within a catalog, so it seems unneeded to make the user select the catalog for which to create the catalog entry (via the drop down list).  The catalog entry resource should nested within the catalog.

You can see the url for creating a catalog entry is /catalog_entries/new which is why the user has to select the catalog for the entry.  If we change this to catalog/1/catalog_entries/new, we can use the catalog id and auto-populate the selection.


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


How reproducible:
Use the admin ui to create a catalog entry, and you'll see a list of catalogs to select from, in which to create the catalog entry.
  
Actual results:
Catalog Entry creation is a top level resource instead of a nested resource, so the user is required to select the catalog twice, once for navigation, and once for the creation screen.

Expected results:
Once you select the catalog in the navigation (drilling down to the catalog entry screen), there should be no reason to ask the user what catalog the catalog entry should be created in.

Additional info:
Comment 2 chris alfonso 2011-10-12 17:51:05 UTC 
commit dcbc0f7ca310c9160d98b87735b1103cc558d582
conductor.git repo
Comment 3 Aziza Karol 2011-10-17 08:37:42 UTC 
The catalog entry resource is nested within the catalog.
Now,the user does not have to select the catalog twice.

verified on:
[root@gs-bl460cg1-01 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
aeolus-all-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch
aeolus-conductor-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
Comment 5 errata-xmlrpc 2012-05-15 22:15:22 UTC 
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/RHEA-2012-0583.html