Bug 606301

Summary: sorting on "avg" response time column doesn't work
Product: [Other] RHQ Project Reporter: Joseph Marques <jmarques>
Component: Core UIAssignee: Joseph Marques <jmarques>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: low    
Version: 3.0.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-12 16:47:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joseph Marques 2010-06-21 11:43:57 UTC
Description of problem:

sorting on "avg" response time column doesn't work

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

* since 1.2.0.GA
* introduced during migration of call-time data view from struts to JSF (commit 95c36729578a222e5d01e6706e91b0be5410a5f4)

How reproducible:
every time.

Steps to Reproduce:
1. Enable response time monitoring for rhq-portal.war resource
1a. Go to monitor>schedules sub-tab for rhq-portal.war resource
1b. Find the schedule whose type column reads "CALLTIME"
1c. Enable it
2. Generate some calltime data events by clicking around the RHQ app
3. Go to monitor>response sub-tab
4. Sort by the column labeled "avg"
  
Actual results:

The ordering of the results is unaffected by the sort

Expected results:

The results should be sorted by the "avg" call-time value.  Clicking the column a second time should toggle ascending / descending.

Comment 1 Joseph Marques 2010-06-21 11:47:12 UTC
commit 3e3928cc20caa685232e31c087bdf040b4619e1a
Author: Joseph Marques <joseph>
Date:   Mon Jun 21 07:42:37 2010 -0400

    BZ-606301: fix sorting for "avg" response-time column (missing left paren)

Comment 2 Corey Welton 2010-06-23 12:38:18 UTC
QA Verified -- sorting appears to now work on this column, both ascending and descending.

Comment 3 Corey Welton 2010-08-12 16:47:27 UTC
Mass-closure of verified bugs against JON.