Issue Summary

Assets object date attributes sometimes display one hour earlier in Object History, which may cause them to display as one day earlier when represented as dates.

Steps to Reproduce

There appear to be some inconsistencies in how dates are stored and processed in attributes, and in how these dates are displayed in Object History. This is one example.

Environment:

• Windows Server 2016
• Java 17
• System Time Zone US Eastern Standard Time automatically adjusted for DST (GMT-4)
• JVM time zone -Duser.timezone=America/New_York OR GMT-4
• Jira user time zone America/New_York

Steps:

1. Create an object with a date attribute called 'Revised'
2. Set the attribute to a value of any date, for example '10-Oct-2025'
3. Edit the attribute delete the value
4. View the Object History

Expected Results

The Object History correctly reflects the attribute's previous value. In the example above, you should see:

Removed the 'Revision' (was 'Fri, 10 Oct 2025')

Actual Results

The Object History reflects that the attribute's previous value was one day earlier. In the example above, you see:

Removed the 'Revision' (was 'Thu, 9 Oct 2025')

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: