Worklog Timer Bug with Operational Hours

Worklog Timer Bug with Operational Hours

When adding a work log using the work log timer feature, it incorrectly evaluates the time when the 'Include non operational hours' box is unchecked. The server's time and time zone are correct

Scenario:

User Personalization Timezone Setting: (GMT-05:00) EST
Admin Operational Hours setting: Start Time 08:00, End Time: 16:30

Work Log Begin: 31 May 2017 (Wednesday) 08:30:00
Work Log End: 31 May 2017 (Wednesday) 08:33:00

Time value, Include non operational hours unchecked: 0 minutes
Time value, Include non operational hours checked: 3 minutes


                New to ADManager Plus?

                  New to ADSelfService Plus?