MySQL Bugs: #44029: If CG area is collapsed, the graph doesn't change with the selection

Bug #44029	If CG area is collapsed, the graph doesn't change with the selection
Submitted:	2 Apr 2009 1:35	Modified:	17 Jul 2009 15:39
Reporter:	Bill Weber	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S3 (Non-critical)
Version:	2.1.0.1022	OS:	Any
Assigned to:	Josh Sled	CPU Architecture:	Any

Description:
On the Quan tab, if the correlation graph area is collapsed, changing the graph selection does not change the graph as it does when the area is expanded.

How to repeat:
- install and run dashboard
- install and run an agent
- go to Query Analyzer page (correlation graph should be visible)
- turn Refresh to "Off"
- change graph to CPU Utilization...graph should change
- collapse CG area (click "-" next to "Graph:")
- change graph selection to Database Activity
- expand CG area (click "+" next to "Graph:")
| notice the graph is still CPU Utilization

Josh Sled writes: 
I can't believe this is higher than P4, though annoying.  Also, targeting 2.1 betas.

Sloan Childers writes: 
While this is not a high priority bug, it is a usability issue which causes confusion and from a usability perspective could actually be marked a higher priority.  Per bug council making a normal priority bug that we'd like to see fixed if possible for 2.1 GA.

Josh Sled writes: 
revno: 7341
revision-id: jsled@asynchronous.org-20090714215444-y2duydnpsxeajrd2
parent: jsled@asynchronous.org-20090714201613-j0hq3xqdykzn7rcq
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Tue 2009-07-14 17:54:44 -0400
message:
  EM-358, Bug#44029: support case where the "cg control" is collapsed and the user changes the CG type.

Keith Russell writes: 
Patch installed in versions => 2.1.0.1077.

Marcos Palacios writes: 
Verified fixed in build 2.1.0.1077.

Was tested on IE 8.0, Safari 3.2 and Firefox 3.0.

An entry has been added to the 2.1.0 changelog:

In the Enterprise Dashboard, in the Query Analyzer tab, the monitored parameter was not handled correctly during collapse and expansion of the graph. For example, if the graph was monitoring CPU Utilization, and then collapsed and the parameter changed to Database Activity, the monitored parameter reverted to CPU Utilization when the graph was expanded again.