Bug 916205 - RFE: "Destinations" and "Versions" of a bundle should not be clickable
Summary: RFE: "Destinations" and "Versions" of a bundle should not be clickable
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-27 14:23 UTC by Lukas Krejci
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Lukas Krejci 2013-02-27 14:23:15 UTC
Description of problem:
See BZ 790226 for further details.

Currently, the "Destinations" and "Versions" nodes in the left navigation tree of the Bundle subsystem bring you to the detail view of the bundle, switching to the appropriate tab on that detail view.

But the overall details of the bundle, placed above those tabs, remains the same. It can be confusing to the user that "Destinations" are selected in the left nav, yet they're looking at the bundle detail page on the right. This might create confusing situations like in BZ 790226, where the user was lead to believe that the "Delete" button on the page relates to the destinations and not the bundle itself. Even though the bundle deletion must further be confirmed in another modal dialog, users can very easily just not read what the system is asking and create unnecessary problems for them.

My suggestion would be to remove the ability to click on "Destinations" and "Versions" nodes in the left nav as they serve merely as grouping nodes without any attached functionality.

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

How reproducible:
always

Steps to Reproduce:
1. Bundle with a destination
2. Click on the "Destinations" in the left nav under the bundle
3. Click "Delete" in the detail page
  
Actual results:
The bundle can be deleted if the user is not careful enough

Expected results:
We should prevent such accidents by not making the "Destinations" node clickable so that we don't make users think they're doing something different than they really are.

Additional info:


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