-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
Seeing a discrepancy in Alert timestamps when switching from GMT-3 to GMT+2
Steps to Reproduce
- Create a dummy Alert
- Note the creation time of the Alert in the Alert details
- Switch to a Timezone that follows Daylight Savings (DST) e.g GMT +2
- Note the creation time of the Alert in the Alert details
- Switch to a Timezone that does not follow Daylight Savings (DST) e.g GMT -3
- Note the creation time of the Alert in the Alert details
Expected Results
We expect the Alert creation time to follow the absolute time difference between the timezones
Actual Results
We are seeing a discrepancy of 1hour when switching to/from a DST timezone
Workaround
No workaround at this moment
- mentioned in
-
Page Loading...
This bug description is not entirely true. It's all about DST. For example, for the Warsaw timezone, GMT+1 should appear in January. If you look at an alert created in January in June, you should see GMT+1. But we show the GMT value in June, which is GMT +2.
Btw we fixed the issue and tested it in staging. we're waiting for the deployment.