Zammad works in the wrong time zone

Old Problem since version 2.5

  • Used Zammad version: 2.9
  • Used Zammad installation source: (source, package, …) DEB
  • Operating system: Debian 8.11
  • Browser + version: actual Firefox

Expected behavior:

  • time management (trigger, sheduler, etc) work with CET

Actual behavior:

  • works with with UTC

Steps to reproduce the behavior:

  • I tried to setup the time zone over Zammad console. But without any result.

In Zammad:

The OS:

#timedatectl
Local time: Thu 2019-03-07 13:06:08 CET
Universal time: Thu 2019-03-07 12:06:08 UTC
RTC time: Thu 2019-03-07 12:06:08
Time zone: Europe/Berlin (CET, +0100)
NTP enabled: no
NTP synchronized: yes
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
Sun 2018-10-28 02:59:59 CEST
Sun 2018-10-28 02:00:00 CET
Next DST change: DST begins (the clock jumps one hour forward) at
Sun 2019-03-31 01:59:59 CET
Sun 2019-03-31 03:00:00 CEST

Console zammad:

Loading production environment (Rails 5.1.6.1)
irb(main):001:0> Time.zone
=> #<ActiveSupport::TimeZone:0x00005643bfc1a5a8 @name=“UTC”, @utc_offset=nil, @tzinfo=#<TZInfo::DataTimezone: Etc/UTC>>
irb(main):002:0> Time.now
=> 2019-03-07 13:27:42 +0100
irb(main):003:0> DateTime.now
=> Thu, 07 Mar 2019 13:28:05 +0100
irb(main):004:0> Time.zone.now
=> Thu, 07 Mar 2019 12:28:23 UTC +00:00
irb(main):005:0>

How I can change this?

=> Thu, 07 Mar 2019 12:28:23 UTC +00:00

Thanks for helping in advance.

JFI: Triggers do not care about the timezone, as they fire at the moment the event happens. This might be a “problem” inside the history.

The scheduler currently runs in UTC and you can’t change this at the moment.
See: https://github.com/zammad/zammad/issues/457

Thanks @MrGeneration

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.