Time seems to be one hour out in tickets

Nexbridge

The time displayed in tickets seems to always be one hour out at the moment - at first I thought it might be a server timezone issue as I'm based in the UK and we're currently on BST (GMT+1) as it's summer time, however the time is displayed correctly on the ticket summary page, so it looks like a bug. I've attached a couple of screenshots below to illustrate - the first is from the individual ticket view (which is incorrect) and the second is from the tabular view on the ticket summary page (which is correct). I know one is a created date and the other a last updated date, but they should be the same in this case as it was a new ticket. FYI the time is an hour out throughout the individual ticket page - in the headers at the top, and in each response.

Thanks

ntozier

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?
php.ini timezone?
database timezone?
agent time zone?
osTicket time zone?

Nexbridge

Please see below as requested:

Environment: Debian 9.4
osTicket version: 1.10.1
php.ini timezone: Europe/London
Database timezone: SYSTEM (BST)
Agent timezone: Europe/London
osTicket timezone: Europe/London

Nexbridge

Also I've just noticed that although it says "Last Updated" in the tabular open ticket summary view, the time in the column is actually the creation time, although that's obviously a separate issue.

ntozier

My guess would be either:
that the database time is set to BST instead of Europe/London.
or
that you are running an ancient version.

Nexbridge

Europe/London is just the PHP timezone for the UK, and it changes from GMT to BST and vice versa in Mar/Oct, so at the moment it's BST.

The fact that the time is correct on the Last Updated column in the tabular open ticket summary view but not within the individual tickets themselves presumably means that the right variable is available, it's just not being used in the latter case? If so then if you can tell me the correct variable name to use, and which variable it should replace and in which file, then presumably I could patch the issue?

Thanks

KevinTheJedi

@Nexbridge

Please login to your database, go to the ost_ticket table, lookup the ticket in your original screenshot by number, and post a screenshot of the created and lastupdate columns.

Cheers.

Nexbridge

Please see below as requested:

ramrajone

Nexbridge
what's your PHP version?
Also, you are running 1.10.1 older version, could you upgrade to 1.10.6 https://osticket.com/download/

Nexbridge

The PHP version is 7.0.27. I could ask about upgrading to 1.10.6, but that would have to be cleared with Net Eng, and they would probably only consider it if it was specifically identified that that would resolve the issue.

Thanks