MantisBT - v2.0 Release (Closed)
View Issue Details
0000447v2.0 Release (Closed)[All Projects] Generalpublic2010-05-25 01:582010-06-21 21:09
Reporterbourbaki007 
Assigned Tocaseydk 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Versionv2.0.0 
Summary0000447: User Log Date Time IN - Date Time OUT: swapped values
DescriptionOn the same report:
                        Date Time IN Date Time OUT
Admin Person 2010-05-19 11:20:42 2010-05-19 13:38:44
Admin Person 2010-05-06 09:57:07 2010-05-06 09:29:53

The first line makes sense.
The second one is wrong since 09:57:07 comes after 09:29:53.
It should be 09:29:53 as IN and 09:57:07 as OUT Time.

Curious: some lines of the same report are ok, others are wrong.
TagsNo tags attached.
Attached Files

Notes
(0000908)
caseydk   
2010-05-29 21:53   
I haven't been able to reproduce this one..

Are these all for the same user? Are you using the same computer each time? Is this the same browser each time?
(0000919)
bourbaki007   
2010-05-31 02:25   
I tried again on the same computer and on another one.
The same behavior on each one. Also with different w2p users.
Also on two different servers (w2p installations): a "real" one (linux) and a virtual machine (XP) on localhost (XP).

Playing around it appears that it's a time shifting issue instead of swapping time values:
When my computer clock shows 10:01, I log into w2p and see that Date Time IN displays 10:31. It's like a forward shift of 30 min.

It seems that also some shifting occurs to Time OUT because while my computer clock shows 11:31 I get on a different log line:
Admin Person 2010-05-31 11:33:03 2010-05-31 11:54:08

The two servers I tried are in time sync.
I'm using Firefox 3.6.3 on Win XP with cookies enabled, but deleting them when exiting.

w2p settings for Admin user:
Locale: english
Timezone: GMT+1 Europe/Vienna
Daylight Savings?: yes
        As of web2project v1.3, timezones are included for information purposes only.No calculations or displayes are affected by setting a timezones.
Tabbed Box View: either
Short Date Format: 31/May/2010
Time Format: 10:29 am
(0000973)
caseydk   
2010-06-06 10:31   
I've tracked down the core of this one. After you've upgraded to database version 19 or above, go into System Admin -> System Configuration and make sure your System Timezone is set properly.

To be clear, this is supposed to be the Timezone of the server itself.

Issue History
2010-05-25 01:58bourbaki007New Issue
2010-05-25 12:17caseydkProjectv1.3 Release (Closed) => v2.0 Release (Closed)
2010-05-29 21:53caseydkNote Added: 0000908
2010-05-29 21:53caseydkStatusnew => feedback
2010-05-31 02:25bourbaki007Note Added: 0000919
2010-06-06 10:31caseydkNote Added: 0000973
2010-06-06 10:31caseydkStatusfeedback => resolved
2010-06-06 10:31caseydkResolutionopen => fixed
2010-06-06 10:31caseydkAssigned To => caseydk
2010-06-21 21:09caseydkStatusresolved => closed
2010-06-21 21:09caseydkFixed in Version => v2.0