Bug 1062244

Summary: [RFE] Display dates and times for "Recent Changes" list on the homepage
Product: [Community] Bugzilla Reporter: Jan Pokorný [poki] <jpokorny>
Component: User InterfaceAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact: Matt Tyson 🤬 <mtyson>
Severity: low Docs Contact:
Priority: low    
Version: 4.4CC: ebaak, jmcdonal, qgong, rjoost
Target Milestone: 4.4   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4.4021 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-07 00:30:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 406661    
Bug Blocks:    

Description Jan Pokorný [poki] 2014-02-06 13:58:11 UTC
As from time to time it can happen that bugzilla suddenly "behaves
differently", I think it would be great to ease a user to correlate
such a change with the deployment of updated RHBZ.  Currently, the
homepage lists only the most recent changes, but furthermore there
is no notion of _when_ it happened.


I think the solutions are (in a subjective order of preference):

a. provide a link to the public ML announcement for the stated
   latest version (note that currently bugzilla-announce-list [1]
   is missing the announcement of 4.4.1013 release)

   - this has an advantage of providing a general direction of
     where to search for older changes, apparently the date of
     deployment is easily deduced from the date of the announcement

b. state the date (preferably considering GMT/UTC zone) when
   the release in question was deployed

   - this would at least provide a hint in a before-after fashion
     for the questioned behavior (nobody really remembers the
     minor versions so as to achieve the same and the mentioned
     bugzilla-announce-list is unfortunately pretty separated ATM)


[1] https://www.redhat.com/archives/bugzilla-announce-list/

Comment 1 Simon Green 2014-02-06 20:38:27 UTC
My vote is for (b) only. The mailing list post provides no additional information than on the home page, and doesn't list internal changes (for those that have privileges to see them).

The date would have to be the server date (US/Eastern) since translation into the users timezone is done at the display level, and not in the code itself)

  -- simon

Comment 2 Jason McDonald 2014-02-07 02:01:47 UTC
Apologies, I managed to send the 4.4.1013 announcemenet to the internal list  I'll correct that momentarily.

Note that if a release does not contain any publically visible changes, there will be an announcment to the internal list but no to the public list.

Comment 3 Simon Green 2014-05-06 01:34:33 UTC
Okay. So the date will be in UTC (and state that) and be the date of the earliest closed bug for that version. I choose earliest since that best represents the time that the bugs were fixed. It cannot be the last in case a bug is reopened and closed again, and an average would suffer from the same version.

Comment 4 Simon Green 2014-07-07 00:30:22 UTC
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon