Bug 846860 - Need a separate button for creating new Destination
Summary: Need a separate button for creating new Destination
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Provisioning, UI, Usability
Version: JON 3.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: JON 4.0.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-08 23:22 UTC by Viet Nguyen
Modified: 2019-06-24 14:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-24 14:53:55 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.