id summary reporter owner description type status priority milestone component version severity resolution keywords cc focuses 35458 current_date returns incorrect timestamp Turn On Social "'timestamp' functionality appears to be wrong. current_time('timestamp') should always return the timestamp according to UTC. That's because a timestamp is defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. Therefore, producing this offset by x number of hours for local time is incorrect logic. If it's 1,452,598,896 seconds since the start of Unix time, this does not change depending on timezone - the number of seconds is the same (but may instead be displayed differently depending on timezone). John mentioned this was so it could be used in date functions but when an incorrect timestamp is fed to a date function, it will display the date wrong (as the timestamp has been artificially manipulated)." defect (bug) closed normal Date/Time normal wontfix reporter-feedback