Wrong date for attachments versions in Confluence 4.5.x
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
After upgrading Confluence from 2.7 to 4.5.3, the attachments versions are all shown with the creation date of the first version.
Cause
In Confluence 2.7 both Creation Date and Last Mod Date were shown.
Upgrading to a newer version makes Confluence show just the the creation date (of the first version) instead of the last modification date.
Workaround
Warning: Backup your database before proceeding.
Before running any SQL in this article, create a full backup of your Jira database. This is a database-level operation with no undo other than restoring from backup. Only proceed if you're comfortable running SQL directly against the Jira database, and test on a staging or cloned environment first, wherever possible.
A simple query should change that:
UPDATE ATTACHMENTS SET creationdate = lastmoddate;By doing that, we are replacing the creationdate to lastmoddate content, which will make confluence pick the correct values.
Was this helpful?