Bug 807811 - Recent Alerts Creation Date format issue - year displayed after time
Summary: Recent Alerts Creation Date format issue - year displayed after time
Keywords:
Status: ON_DEV
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-28 19:41 UTC by Mike Thompson
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version: 4.5.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
Recent alert creation date format error (179.90 KB, image/jpeg)
2012-03-28 19:41 UTC, Mike Thompson 		no flags Details
View All

Description Mike Thompson 2012-03-28 19:41:33 UTC 
Created attachment 573437 [details]
Recent alert creation date format error

The date format is different from the dates elsewhere.

Displays as:

Friday Mar 23 08:46:15 PDT 2012

Note how the year displays after the timestamp.

Also, this is a long date/time format that is not usually dislayed in applications (maybe only in ls command). A more easily read and succinct format would be MM/DD/YY HH:MM:SS TMZ (account for locale differences of course). Jaggies also occur with the fields not visually lining up because the 
Not sure if this last issue is anything or not just thought I would bring it up.

See Attachment of screenshot.
Comment 1 Charles Crouch 2012-03-29 19:37:08 UTC 
We should just be using the same date format we do everywhere else right?
Note You need to log in before you can comment on or make changes to this bug.