Bug 1341740 - inconsistency on the monitoring button between pages
Summary: inconsistency on the monitoring button between pages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: GA
: 5.7.0
Assignee: zakiva
QA Contact: Gilad Shefer
URL:
Whiteboard: container
Depends On:
Blocks: 1342222
TreeView+ depends on / blocked
 
Reported: 2016-06-01 16:16 UTC by Dafna Ron
Modified: 2018-06-06 11:37 UTC (History)
10 users (show)

Fixed In Version: 5.7.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1342222 (view as bug list)
Environment:
Last Closed: 2017-01-11 19:54:56 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshots (1.12 MB, application/x-gzip)
2016-06-01 16:16 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2016-06-01 16:16:40 UTC
Created attachment 1163742 [details]
screenshots

Description of problem:

When you expend the monitoring button, in some pages the timeline is first and Utilisation is second and in other pages it's reversed. 

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

cfme-5.6.0.8-rc1.1.el7cf.x86_64

How reproducible:

100% 

Steps to Reproduce:
1. navigate to compute -> container -> provider -> select provider -> monitoring  
2. navigate to compute -> container -> containers -> select container -> monitoring
3.

Actual results:

in providers the utilization appears before the timeline and in containers the timeline appears before the utilization. 

Expected results:

we should have consistency on all pages 

Additional info: screenshots

I checked all the pages and the utilization appears first in both providers and in nodes 


This might be a fast easy fix so putting 5.6z flag

Comment 2 zakiva 2016-06-08 11:59:57 UTC
Bug fix: https://github.com/ManageIQ/manageiq/pull/9142

Comment 3 Federico Simoncelli 2016-07-12 09:13:03 UTC
Shouldn't this be in POST?


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