Bug? In Tasks

m-law

I've posted this over at Github also. Apologies if it is not in the correct format:

Version 1.18.1

After creating a task, if I change the time it is due, it will not update to the time I selected. It updates to an hour afterwards.
Example - if I change the due date to 5PM, is saves as 6PM.
This was noted when I had meant to save for 12AM an item on 19th September 2024. It would save as 1AM. Then the only way to get it to update to 12AM was to select 18th September and 11PM.
But I noted, trying various different times, it constantly updated to 1 hour after.

KevinTheJedi

m-law

What are your Agent Profile, system, database, PHP, and server timezones?

Also, take note of your database timezone, go to the _task table, find a record in the db where you know the time is showing incorrectly, convert the timestamp from the database time zone to your timezone, and see if it’s accurate.

Cheers.

m-law

KevinTheJedi Thanks. I'll do a bit more digging. It was actually on a secondary OST installation I've recently installed where I had not set the correct time zone in Linux or my PHP.ini

I never realised this until after I posted but changed it and rebooted the server. Still an issue although Europe/London is my Timezone now in my PHP settings (showing in OST info tab). It's set this way in Linux also. My OST agent profile is set as Europe/London, as is the system setting.

The only thing I see set as UTC still is the Database timezone. So I intend to try changing that when I get time. Am running in Docker so am guessing I'll need to bash into the MariaDB container and do something from what I read briefly online (not looked into it yet properly).

KevinTheJedi

m-law

UTC is actually best for database time zone. That way all times can be easily converted to any time zone.

Cheers.

m-law

Hi, managed to resolve it. I noticed another forum user had the same issue.
Long story short, they posted the below as the solution, which has worked for me:
https://github.com/osTicket/osTicket/issues/3991#issuecomment-337910462

KevinTheJedi

m-law

That change is already in the code. You would simply need to update your @@global.time_zone variable in your database to your desired timezone. Full timezone names work best (eg. America/Chicago, Asia/Tokyo, etc.).

Cheers.

m-law

Noted thanks!