Bug 1182014 - The Last Closed described in history isn't shown by user time zone
Summary: The Last Closed described in history isn't shown by user time zone
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
: 1197524 1248205 1328666 1516948 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-14 10:11 UTC by Rony Gong 🔥
Modified: 2018-12-09 06:29 UTC (History)
7 users (show)

Fixed In Version: 5.0.4-rh2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-18 10:14:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Rony Gong 🔥 2015-01-14 10:11:00 UTC
Description of problem:
The Last Closed described in history isn't shown by user time zone

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Login as a user whose timezone is set as CST time(Asia/Shanghai)
2.Close a bug, then check the Last Closed described both in inline history and activity history 
3.

Actual results:
Last Closed: 2015-01-14 05:01:17

Expected results:
Last Closed: 2015-01-14 18:01:17 CST

Additional info:

Comment 1 Jason McDonald 2015-01-15 01:33:12 UTC
Seems we missed the detailed history page when addressing Bug 1015377.  Compare the Last Closed date displayed (correctly) on the bug page with the value displayed (incorrectly) on https://bugzilla.redhat.com/show_activity.cgi?id=1015377.

Comment 2 Jason McDonald 2015-03-02 04:23:13 UTC
*** Bug 1197524 has been marked as a duplicate of this bug. ***

Comment 3 Jason McDonald 2015-03-02 05:02:12 UTC
The timestamp returned by the Bug.history RPC call should also include timezone information.

Comment 4 Matt Tyson 🤬 2015-04-10 00:58:09 UTC
The history column is a varchar field, not a timestamp.  Making this behave as the users expect might be tricky, we'd have to try and grub it out in code and flip it around to what the user expects.

Comment 5 Jason McDonald 2015-07-30 00:51:19 UTC
*** Bug 1248205 has been marked as a duplicate of this bug. ***

Comment 6 Jeff Fearn 🐞 2016-06-30 03:02:19 UTC
*** Bug 1328666 has been marked as a duplicate of this bug. ***

Comment 8 Matt Tyson 🤬 2017-11-23 23:00:06 UTC
*** Bug 1516948 has been marked as a duplicate of this bug. ***

Comment 9 Jeff Fearn 🐞 2018-03-16 03:28:16 UTC
Hi John, do you know what is the correct use and behavior of this field?

Comment 10 Jeff Fearn 🐞 2018-03-19 02:58:08 UTC
Sigh, that question  in #9 was for the wrong bug >_<

Comment 11 Jeff Fearn 🐞 2018-04-11 06:26:28 UTC
Now displays as:

Last Closed 		2014-02-03 20:13:36 UTC 

As I have my time pref set to UTC.

Comment 12 Jeff Fearn 🐞 2018-04-18 10:14:59 UTC
This bug has been resolved in Red Hat Bugzilla 5 and can be tested on https://beta-bugzilla.redhat.com

If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.


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