Fossil: View Ticket

Ticket UUID:	bf4f5725f6c90fc2a113e35acde27e25e6b290b2
Title:	Tickets: cannot display in local time
Status:	Fixed	Type:	Code_Defect
Severity:	Important	Priority:
Subsystem:		Resolution:	Fixed
Last Modified:	2010-12-30 10:00:44
Version Found In:	0018d724b3
Description & Comments:
All the times in the ticket reports and comments are in UTC. Admin/Timeline/Use UTC settings has no effect. I try to convert the time to local in SQL with something like this (syntax suggested by sqlite docs) SELECT datetime(tkt_mtime, 'localtime') AS 'mtime' FROM ticket and get the following error error code 23: access to config.value is prohibited Database Error access to config.value is prohibited SELECT value FROM config WHERE name='timeline-utc' If you have recently updated your fossil executable, you might need to run "fossil all rebuild" to bring the repository schemas up to date Running 'fossil all rebuild' does not help. Is this a bug or am I missing the proper way to convert timestamps to local time? anonymous added on 2010-12-27 13:15:05: Duplicate of [5c1490e26b]. The time is written as a string part of the comment. anonymous added on 2010-12-28 10:28:50: That ticket does not mention that tkt_mtime (last modified timestamp) is in UTC too. And it would be nice to have a way to see local time everywhere. anonymous claiming to be Arnel added on 2010-12-28 18:20:16: How about going to Admin > Timeline then unchecking the "Use Universal Coordinated Time (UTC)" option for both the server and the local repo? anonymous claiming to be Alex added on 2010-12-29 06:20:03: Tried that. Does not make any difference. Neither for mtime field in the ticket table, nor for "username added on date" on the edit ticket page. anonymous claiming to be viric added on 2010-12-29 08:26:12: The "comment added by XXX on YYY" has nothing to do with any timestamp stored in a database. It's a text message added automatically over whatever comment the user did on a ticket or wiki page. So its contents are stored 'statically', and no option will change them later. If you agree that this is the same issue as in [5c1490e26b], we can close this and keep the discussion there. anonymous claiming to be Alex added on 2010-12-29 10:44:03: I understand that the time a comment was added is part of its text and cannot be easily converted into a different timezone or format. Correct formatting has to be done before a comment is added to the repo, be it automatically or by calling some functions in the script (we just need to know which ones). Speaking of duplicates, 5c1490e26b only describes one thing, the comment timestamps. This ticket suggests that the entire UTC/local conversion is somehow broken. A developer has to take a look to say whether a single common defect or two unrelated ones are causing the effects. If you are concerned about the number of open tickets, you can close any of the two and I will copy the info into the other ticket (not that it would make any sense with so many tickets left open already). anonymous claiming to be Alex added on 2010-12-30 10:00:44: Fix in commit 8c3bba8e97 confirmed. Thanks, DRH!