Project

General

Profile

Actions

Feature #19047

closed

Unify the way how we display dates

Added by Marek Hulán over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Reporting
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1435973

When checking last report in `/config_reports?search=eventful+%3D+true` the column "Last report" it only shows the time since this config run was execueted. If multiple runs are made in a given time it's very difficult to understand which one belongs to which run.
To figure out which run was made at which time, one needs to select the report to get this information. It would be therefore nice to report actual time/date of the `puppet` run instead of "ago". So having an option to set "Last Report" to "Reported at" which then would give time and date, would be appreciated.

When multiple runs are done in short or also when something is happening on a host it's difficult to quickly elect the right report in the UI. Having real time and date it's easier to understand when a `puppet` run happen and therefore find quickly the right report to check.
Having "Last Report" reporting the real time instead of the time that elaps since the last `puppet` run would ease that task and avoid lot's of unecessary clicking in the UI

We should either provide time/date in "Last Report" by default or provide a switch where the functionality can be enabled globally. Meanding for all kind of report that are showing this behavior.

"Last Report" should show "2017-03-22 07:19:37 UTC" or similar instead of "4 days ago"


Related issues 12 (4 open8 closed)

Related to OpenSCAP - Refactor #21038: Ensure dates are printed consistently with coreClosed09/20/2017Actions
Related to Foreman - Refactor #21039: Ensure dates are printed consistently with coreClosedAdi AbramovitchActions
Related to virt-who configure - Refactor #21040: Ensure dates are printed consistently with coreClosedActions
Related to Discovery - Refactor #21041: Ensure dates are printed consistently with coreClosedDominik MatoulekActions
Related to Docker - Refactor #21042: Ensure dates are printed consistently with coreNew09/20/2017Actions
Related to Foreman Remote Execution - Refactor #21043: Ensure dates are printed consistently with coreNew09/20/2017Actions
Related to Katello - Bug #21045: Ensure dates are printed consistently with coreClosedTomáš StrachotaActions
Related to foreman-tasks - Refactor #21044: Ensure dates are printed consistently with coreNew09/20/2017Actions
Related to Foreman - Bug #21213: not view certs in puppetca on smart proxyClosedMarek Hulán10/05/2017Actions
Related to Foreman - Feature #21312: Foreman should provide react components for formatting datesClosedTomáš StrachotaActions
Related to Foreman - Feature #21497: As discussed on PR that introduced date helpers, we should make date format configurable on few placesNew10/27/2017Actions
Related to Foreman - Bug #26113: Smart proxy log times not displayed.ClosedTomer BriskerActions
Actions

Also available in: Atom PDF