Please help us to help you by reading and following the posting guidelines located in this thread: Please read before requesting assistance. The more information you give us the better we will be able to assist you. Thank you.

Environment details?
Version of osTicket?
MySQL timezone?
Agent profile timezone?

5 days later

Sorry:

Linux Ubuntu 18.04
osTicket 1.14.1
Agent profile timezone (osTicket) ????????? Where is this setting
Web Server Software Apache/2.4.29 (Ubuntu)
MySQL Version 5.7.28
MySQL Timezone SYSTEM
System timezone Australia/Brisbane AEST +10
PHP Version 7.2.24-0ubuntu0.18.04.1

It's in your Agent profile.
Upper right hand corner. Click profile.

5 days later

Agent profile set correctly, still one hour behind.
osTicket, PHP, and SQL all set as Australia/Brisbane

Update:
In Settings I have it set to Australia/Brisbane, but in the system information it says, under Databse, "Timezone AEST (Interpreted as Australia/Melbourne)". Will continue to investigate my sql settings.

Update2:
Running mysql -u osticket -p -e “SELECT NOW();” returns the correct time.
Running SELECT @@global.time_zone; Returns Australia/Brisbane
I have set all the variables to either '+10:00' or 'Australia/Brisbane' (including in etc/mysql/my.cnf) but its still being "interpreted as Australia/Melbourne"

Consistent with: https://forum.osticket.com/d/92063-time-problem/5

    @squiz

    Post your Server's timezone. When MySQL is set to SYSTEM we use the server's timezone to store date/times in the DB. Then we convert the time from the DB (which is in the server's timezone) to whatever is set on the Profile/System Default when we display the results on the screen.

    Cheers.

    5 days later

    Are you looking for something different than what I have posted above (my second post in this thread)?

    Server time zone. Controlled by the operating system on the server.

    $ timedatectl status

    Local time: Thu 2020-01-30 13:32:07 AEST
    Universal time: Thu 2020-01-30 03:32:07 UTC
    RTC time: Thu 2020-01-30 03:32:07
    Time zone: Australia/Brisbane (AEST, +1000)
    System clock synchronized: no
    systemd-timesyncd.service active: yes
    RTC in local TZ: no

      5 days later

      I wasn't after anything. I was clarifying on @KevinTheJedi post that you asked a question about.

      Thanks Kevin Yes I have completed all of those, setting each to Australia/Brisbane, which is +10.

      The issue is here:

      mysql> SELECT @@GLOBAL.time_zone, @@SESSION.time_zone;
      +--------------------+---------------------+
      | @@GLOBAL.time_zone | @@SESSION.time_zone |
      +--------------------+---------------------+
      | Australia/Brisbane | Australia/Brisbane |
      +--------------------+---------------------+

      In my osTicket system information
      PHP Settings
      date.timezone Australia/Brisbane

      Database Information
      Timezone AEST (Interpreted as Australia/Melbourne)

      9 days later

      @squiz

      So after making those changes, new tickets times are off or old tickets? This should affect new tickets and not old tickets as old tickets have the old db timezone.

      Cheers.

      10 days later

      @KevinTheJedi
      Yes new tickets are still off by 1 hour, according to Australia/Melbourne time as suggested in the oSTicket settings.

      @KevinTheJedi
      Yes, from my settings (above) you can see that everything is listed (and set) as Australia/Brisbane