Bug 1432244 - No active links on VMDB Summary page
Summary: No active links on VMDB Summary page
Keywords:
Status: CLOSED DUPLICATE of bug 1432239
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Martin Povolny
QA Contact: Nandini Chandra
URL:
Whiteboard: ui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-14 21:29 UTC by Nandini Chandra
Modified: 2017-05-31 07:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-29 09:49:33 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nandini Chandra 2017-03-14 21:29:25 UTC
Description of problem:
----------------------
In the VMDB Summary page,hovering the mouse over the values in the following tables brings up a hand pointer.Clicking on this should take you to the table summary page.But, it does not.

Tables with the Most Rows, Largest Tables, Tables with Most Wasted Space 


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


How reproducible:
----------------
Always


Steps to Reproduce:
-------------------
1.
2.
3.


Actual results:
--------------
No active links on VMDB Summary page.


Expected results:
-----------------
Active links on VMDB Summary page


Additional info:
----------------

Comment 3 Martin Povolny 2017-03-29 09:49:33 UTC
Looks top me like a dup for https://bugzilla.redhat.com/show_bug.cgi?id=1432239

the layout of the DIV was broken and it should be fixed by the same fix

https://github.com/ManageIQ/manageiq-ui-classic/pull/801

Found on the same page by the same QE engineer on the same day in the same DIV so maybe next time this could be a single BZ, please?

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


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