Skip to content

Date / time isn't represented accurately on the frontend when using postgres #1569

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
NeurekaSoftware opened this issue Apr 7, 2025 · 5 comments · Fixed by #1654
Closed
1 task done
Labels
bug Something isn't working confirmed This bug has been reproduced

Comments

@NeurekaSoftware
Copy link

NeurekaSoftware commented Apr 7, 2025

Description

Date / time isn't represented accurately on the frontend when using postgres

Version

2.5.2

Steps to Reproduce

  1. Do anything that creates a datetime in the database (postgres only)
  2. See that the datetime is not displayed correctly on the frontend.

Screenshots

Image

Logs

Platform

desktop

Database

PostgreSQL

Device

Desktop

Operating System

Windows 11 Pro

Browser

Edge

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@NeurekaSoftware NeurekaSoftware added awaiting triage This issue needs to be reviewed bug Something isn't working labels Apr 7, 2025
@NeurekaSoftware NeurekaSoftware changed the title Issue creation time is 7 hours ahead Requests / Issue creation time is 7 hours ahead Apr 7, 2025
@fallenbagel
Copy link
Owner

This is not a bug that is limited to issues. It only happens with postgresql because of the without timezone handling in db while not factoring that in when displaying. This issue is not there for sqlite. This issue is present everywhere that a created date is used from the db.

Would you mind editing this bug report to talk about that and not just issues? As this is not a bug with issues per se but postgresql?

@NeurekaSoftware NeurekaSoftware changed the title Requests / Issue creation time is 7 hours ahead Created date / time is broken when using postgres Apr 7, 2025
@NeurekaSoftware
Copy link
Author

Would you mind editing this bug report to talk about that and not just issues?

@fallenbagel does that look better?

Thank you for the quick response.

@NeurekaSoftware NeurekaSoftware changed the title Created date / time is broken when using postgres Date / time is broken when using postgres Apr 7, 2025
@NeurekaSoftware NeurekaSoftware changed the title Date / time is broken when using postgres Date / time isn't represented accurately on the frontend when using postgres Apr 7, 2025
@NeurekaSoftware
Copy link
Author

Do we know if this will be addressed soon? Issues are really broken because of this. 😭

@fallenbagel
Copy link
Owner

Do we know if this will be addressed soon? Issues are really broken because of this. 😭

Yes. This fix will be available for next version.

@NeurekaSoftware
Copy link
Author

NeurekaSoftware commented Apr 11, 2025

Do we know if this will be addressed soon? Issues are really broken because of this. 😭

Yes. This fix will be available for next version.

Awesome!!! Thank you!

@fallenbagel fallenbagel added confirmed This bug has been reproduced and removed awaiting triage This issue needs to be reviewed labels May 6, 2025
fallenbagel added a commit that referenced this issue May 9, 2025
…st-first

Switch key datetime columns to TIMESTAMPTZ for proper UTC handling
(“just now”) and sort issue comments on load so the original
description stays first and in proper sorted order in fix-pgsql-timezone

fixes #1569, fixes #1568
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed This bug has been reproduced
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants