Bug 692136

Summary: date/time columns need to be consistent across the ui
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: Core UIAssignee: John Mazzitelli <mazz>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: 4.0.0.Beta1CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-02 03:14:57 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 585306    

Description John Mazzitelli 2011-03-30 10:10:32 EDT
We have date/time columns all throughout the UI, however, they are not consistent with the format they display. We need to make it consistent.
Comment 1 John Mazzitelli 2011-03-30 10:40:20 EDT
some classes that have date columns in tables, data sources or form static items.

i did a search for usages of all "date" and "time" related I18N messages from Messages and I found these classes:

...inventory.groups.detail.GeneralProperties
...inventory.groups.detail.configuration.HistoryGroupResourceConfigurationMembers
...inventory.groups.detail.configuration.HistoryGroupResourceConfigurationTable
...inventory.groups.detail.inventory.HistoryGroupPluginConfigurationMembers
...inventory.groups.detail.inventory.HistoryGroupPluginConfigurationTable
...inventory.groups.definitions.GroupDefinitionListView
...inventory.groups.definitions.GroupDefinitionDataSource
...inventory.resource.detail.configuration.AbstractConfigurationHistoryDataSource
...inventory.resource.detail.summary.ResourceErrorsView
...inventory.resource.discovery.AutodiscoveryQueueDataSource
...inventory.common.detail.operation.history.AbstractOperationHistoryDetailsView
...inventory.common.detail.operation.history.AbstractOperationHistoryDataSource
...inventory.common.detail.operation.schedule.AbstractOperationScheduleDataSource
...inventory.common.detail.operation.schedule.AbstractOperationScheduleDetailsView
...bundle.deployment.BundleResourceDeploymentHistoryListView
...bundle.destination.BundleDestinationDataSource
...bundle.destination.BundleDestinationListView
...bundle.deployment.BundleDeploymentListView
...bundle.deployment.BundleDeploymentDataSource
...dashboard.portlets.recent.imported.RecentlyAddedResourceDS
...dashboard.portlets.recent.imported.RecentlyAddedResourcesPortlet
...operation.RecentOperationsDataSource
...operation.ScheduledOperationsDataSource
...alert.definitions.AbstractAlertDefinitionsDataSource
...alert.AlertDetailsView
...alert.AlertDataSource
...util.message.MessageCenterView
Comment 2 John Mazzitelli 2011-03-30 21:04:37 EDT
we need to make sure all time/date columns utilize the TimestampCellFormatter API.

The goal is for all time/date columns to use the MEDIUM date format, with a hover to show the FULL date format.
Comment 3 John Mazzitelli 2011-04-01 09:48:41 EDT
took jay's work on TimestampCellFormatter and added to it. then went thru all classes that dislpay times/dates and made them consistent where it made sense.
Comment 4 Heiko W. Rupp 2013-09-02 03:14:57 EDT
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.