You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A user reported that since the timezone update, there is a discrepancy in the displayed train schedule on their profile. When viewing the profile without logging in, a train scheduled for 19:10 is incorrectly shown as 17:10. However, upon logging in, the correct time of 19:10 is displayed for the same train journey.
To Reproduce
Steps to reproduce the behavior:
Visit the user's profile in an unlogged state.
Locate the train departure time for a specific train, e.g., 19:10.
Observe that the displayed time is incorrect, showing 17:10 instead.
Expected behavior
The user expects that the displayed train schedule in both logged-in and unlogged states should consistently show the correct departure time of 19:10.
Screenshots
//
Desktop (please complete the following information):
//
Smartphone (please complete the following information):
//
Additional context
Internal Ticket #220064
The text was updated successfully, but these errors were encountered:
Hi guys,
Since the timezone feature came up, trains show a different time when I’m logged out (minus 2 hours) than when I’m logged in into my profile.
I attached two pictures to this message to show you the problem.
Cheers, Tobi
Temporary fix w/ #1963 - This will only be fixed, once we can handle all date/time formatting in the frontend. A better backend time formatting is just not worth it in this case.
Describe the bug
A user reported that since the timezone update, there is a discrepancy in the displayed train schedule on their profile. When viewing the profile without logging in, a train scheduled for 19:10 is incorrectly shown as 17:10. However, upon logging in, the correct time of 19:10 is displayed for the same train journey.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The user expects that the displayed train schedule in both logged-in and unlogged states should consistently show the correct departure time of 19:10.
Screenshots
//
Desktop (please complete the following information):
//
Smartphone (please complete the following information):
//
Additional context
Internal Ticket #220064
The text was updated successfully, but these errors were encountered: