Bug 1460864 - Menu items are not context aware for Ceph and Gluster [RFE]
Summary: Menu items are not context aware for Ceph and Gluster [RFE]
Keywords:
Status: CLOSED DUPLICATE of bug 1461137
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: Dashboard
Version: 3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: beta
: 3
Assignee: Neha Gupta
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-13 01:49 UTC by Jeff Applewhite
Modified: 2017-06-15 14:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-15 14:33:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeff Applewhite 2017-06-13 01:49:25 UTC
Description of problem:
The menu items in console 3 show items that are not pertinent to the storage backend

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

How reproducible:
always

Steps to Reproduce:
1. view menus
2.
3.

Actual results:


Expected results:
see
https://github.com/Tendrl/dashboard/issues/424
Please update all the "File Share" references in the UI to "Volume" in the UI. This includes the following:

Menu item for "Volumes"
Volumes List view
Create Volume
Edit Volume
Delete Volume
Rebalance Volume
Start / Stop Volume
Object Details view where there is a "Volume" tab (e.g. Gluster cluster object details
Any tooltip with the "volume" reference
Specifically, if I'm a Gluster user, I may get confused by the "File Share" reference as all Gluster documentation references the term "Volume" and we will want to be consistent with Gluster terminology.

Additional info:

Comment 3 Ju Lim 2017-06-15 14:25:37 UTC
This is actually 2 BZ's:

(1) Address context-sensitive menus and navigation (and dashboard) -- see BZ 1461876.

(2) Relabeling "File share" to "Volume" -- see BZ 1461137

Comment 4 Jeff Applewhite 2017-06-15 14:33:07 UTC

*** This bug has been marked as a duplicate of bug 1461137 ***


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