Bug 846860

Summary: Need a separate button for creating new Destination
Product: [JBoss] JBoss Operations Network Reporter: Viet Nguyen <vnguyen>
Component: Provisioning, UI, UsabilityAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED EOL QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: unspecified    
Version: JON 3.1.1CC: jshaughn, loleary
Target Milestone: ---Keywords: UserExperience
Target Release: JON 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-24 14:53:55 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Viet Nguyen 2012-08-08 23:22:12 UTC 
Description of problem:

There are two buttons labeled Deploy in Bundles view

1.  xzy bundle -> Destinations -> Deploy
2.  xyz bundle -> Destinations -> some destination -> Deploy

I found it confusing.  They're not doing exactly the samething. In #1 you must always have to create a new unique destination as there is no dropbox to select existing ones.  

I suggest creating just 1 deployment wizard with a top progress indicator and clearly define concrete steps, eg 1. select/upload bundle, 2. select/create new destination, 3. select bundle version, 4. specify additional options, etc.  The wizard then can be launched (with appropriate info filled in) from top level Bundles view or in destination details view.
Comment 2 Jay Shaughnessy 2014-08-22 19:01:18 UTC 
Bundle wizard usability work would be pending the future of provisioning as a JON feature. Pushing due to time constraints and future provisioning  design.
Comment 3 Filip Brychta 2019-06-24 14:53:55 UTC 
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.