We have updated to 5.2.2 (-1664451892.bca42243.buster), but the behavior is still the same. As nanathlor has mentioned, it’s only in the ticket itself, everywhere else the dates are displayed correctly.
Is date-picker (“js-timepicker”) maybe causing the Problem?
I have the same problem but not only with the field “Waiting for customer” but also with other fields where a date has to be stored in a ticket.I have tested the whole thing on several browsers and everywhere the wrong format is output.
Currently we are using Version 5.2.x and plan to update to Version 5.3.x in January.
Is it possible that this bug only occurs with self-hosted Zammad servers? On a non-self-hosted Zammad server, the date is correct. Again, I am using the same browser.
No that shouldn’t be that specific on that regard.
Make sure you compare the same versions, SaaS is on 5.3 and the version I’ve tested is as well.
I’m not verifying older versions as they’re out of support anyway.
We noticed the same issue on our side after upgrading to 5.3.1.
There was one entry for FORMAT_DATETIME (in de-de), but none for FORMAT_DATE.
Running Translation.sync synced all translations to the database. We went from ~1.7k to ~151k rows.
Afterwards we got entries for FORMAT_DATE and the UI showed the correctly formatted date.
(Also a different environment of ours running the same version had ~3.1k rows).
Not sure how many entries are expected to be in the database.
Previous version was 5.2.3, but the database state was probably even older, as we had one failing migration script (20220124141828_overview_updates.rb, because some of our default overviews did not have roles assigned). With the update to 5.3.1 Zammad crashed and we noticed the failing script, fixed the issue and ran all pending migrations.
Wow Joschasa, THANK YOU! I have now finally been able to “fix” this problem, after what feels like forever!
I truncated the translations table and ran the Locale.sync command and what do you know, the date is now being displayed correctly. It seems I also had the upgrade problem, I do remember, I once got a SQL error message to do with the translations (duplicate id 66841, FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »translations_pkey«).