In mid-November 2019, while trying to run employee call logs from October 2019 (prior to the 11/3/19 Daylight Savings time conversion), all call times are off by 1 hour (early). It seems that, after Daylight Savings passed on 11/3/19, any call log reports run after that point, with a target timeframe from before DST, the RingCentral system subtracts 1 hour from each call start time (presumably because we "fell back 1 hour" on 11/3/19).
Isn't your system sophisticated enough to know that DST has taken place, and adjust the call times? It shouldn't be subtracting an hour for calls being run in a report that took place prior to DST... the calls were at the time they were at, not an hour earlier.
For example... our company has team meetings every Tues. @ 12pm ET. All team calls after Nov. 3 reflect 12pm ET start for each participant. However, all Tues. meetings prior to DST show 11am ET start time, which is incorrect.
Please advise and correct this bug in your call log system.
Isn't your system sophisticated enough to know that DST has taken place, and adjust the call times? It shouldn't be subtracting an hour for calls being run in a report that took place prior to DST... the calls were at the time they were at, not an hour earlier.
For example... our company has team meetings every Tues. @ 12pm ET. All team calls after Nov. 3 reflect 12pm ET start for each participant. However, all Tues. meetings prior to DST show 11am ET start time, which is incorrect.
Please advise and correct this bug in your call log system.