Project versions timestamps are one day behind in the database
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The project versions dates in the database don't match the ones in the UI.
For instance, a version release date of 20/Dec/2017 will show as 12/19/2017 20:00:00 in the database.
Cause
The time in the database will account for the difference in number of hours between the timezone of the database server and the timezone of the Jira server.
Examples
Jira timezone | DB timezone | Release date in UI | Release date/time in the DB |
|---|---|---|---|
UTC | EST (not EDT) | 20/Dec/2017 | 12/19/2017 19:00:00 |
CEST | CDT | 20/Dec/2017 | 12/19/2017 17:00:00 |
Note
Updating the timezone of the DB server will update the times in the DB.
Was this helpful?