Bug 755019 - actions in bundle deployment log Table should be sorted chronologically
Summary: actions in bundle deployment log Table should be sorted chronologically
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.2
Hardware: Unspecified
OS: Unspecified
low
medium vote
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: jon30-bugs jon30-sprint10, rhq43-sprint10
TreeView+ depends on / blocked
 
Reported: 2011-11-18 15:11 UTC by Ian Springer
Modified: 2013-08-06 00:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:20:25 UTC


Attachments (Terms of Use)
screenshot (157.45 KB, image/png)
2011-11-18 15:12 UTC, Ian Springer
no flags Details

Description Ian Springer 2011-11-18 15:11:11 UTC
They are currently not sorted at all. See attached screenshot.

Comment 1 Ian Springer 2011-11-18 15:12:09 UTC
Created attachment 534410 [details]
screenshot

Comment 2 John Mazzitelli 2011-12-06 21:25:52 UTC
master commit: 8a2f8f8

there is one minor issue - there appears to be a smartgwt bug where the sort direction is set to ascending, but the icon that shows up is the down arrow (meaning, it looks like its sorted in descending order). In my testing, however, it really is sorted in ascending order (which is what we want).

When we upgrade to smartgwt 2.5, hopefully, that minor nuisance is fixed.

But aside from the reversed icon that shows in the column's header cell, this bug is fixed - the audit trail is now sorted on the timestamp field.

Comment 3 Sunil Kondkar 2011-12-13 10:49:00 UTC
Verified in latest master build#829 (Version: 4.3.0-SNAPSHOT Build Number: 35fcafb)

The audit trail is sorted by default on the timestamp field in ascending order. Verified sorting is working on all columns in audit trail.

Comment 4 Mike Foley 2012-02-07 19:20:25 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


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