A forum for technical support discussion related to Fogbugz.
I have recently upgraded from v5 to v6 and unfortunately have noticed a problem with the upgrade, something which I rely on as a feed to an external invoicing process.
The dates seem to have been altered by an hour for date fields such as the dtOpened field on the db0.Bug table.
V6: 2007-01-02 23:00:00.000
v5: 2007-01-03 00:00:00.000
This is consistent for all date fields.
The 'simple' resolution is for me to update all date fields +1 hour, but I would like to know why this has happened as I would not expect the upgrade to modify my existing data.
Just an addendum to this, it does appear that british summer time is not being taken into account when picking up the time zone settings from the server. My Fogbugz server is currently set to GMT, with the 'daylight saving' option checked to adjust for British Summertime. But when I go into the 'Site Configuration' > 'Regional' > 'Timezone' option, the setting says "Choose Use Server's Time Zone to use this server's setting, currently (GMT) GMT Standard Time", but no reference to daylight saving.
My concerns here are that the upgrade changed the data, and if a case was logged around mignight, it is now moved to the previous day, which is surely wrong.
I think this is because all dates in the db are now stored in universal time zone (or regular old GMT with now daylight savings time). You happen to be in GMT so you are seeing the GMT offset for DST, but we're storing them in the universal time zone so that doesn't apply. This is because the conversion to timezone is now done on the client -- so different people can see FogBugz from their own perspective.
Michael H. Pryor
Thursday, September 6, 2007
This topic is archived. No further replies will be accepted.Other recent topics