[ZBX-22616] Clock widget default timezones give wrong time Created: 2023 Mar 30  Updated: 2023 Apr 06

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 6.4.0
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Waleed Mortaja Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 0
Labels: frontend
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-03-30-11-31-37-847.png     PNG File image-2023-04-02-11-54-56-781.png     PNG File screenshot-1.png     PNG File screenshot-2.png     PNG File screenshot-3.png     PNG File screenshot-4.png     PNG File screenshot-5.png     PNG File screenshot-6.png    

 Description   

Steps to reproduce:

  1. Add two clock widgets
  2. Select time type of local time for both of them
  3. Enable advance configurations for both of them
  4. For one of the clocks select timezone of "System default: (UTC+00:00) UTC"
  5. For the other clock, select timezone of "(UTC+00:00) UTC" (not the system default)
  6. You can add two more clocks with time type of server time. It has the same results.

Result:
The "System default: (UTC+00:00) UTC" clock shows time different than the time of "(UTC+00:00) UTC". The non-default timezone is the correct time. See the screenshot.


Expected:
Both "System default: (UTC+00:00) UTC" and "(UTC+00:00) UTC" should show the same correct time.

 

Also:
"Local default" timezone seems to be NOT respecting the Daylight Saving Time changes.



 Comments   
Comment by Michal Czerniakiewicz [ 2023 Mar 31 ]

Can not reproduce. There is no difference in the time being shown all clocks are in sync.




Comment by Waleed Mortaja [ 2023 Apr 02 ]

It seems to be dependent on the timezone selected in Administration --> General --> GUI. I used a timezone of +7h and got new clocks.

Comment by Michal Czerniakiewicz [ 2023 Apr 06 ]

I can confirm. Changed default timezone in front-end GUI for UTC+07:00 Asia/Bangkok.

Generated at Mon Apr 28 09:15:53 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.