JIRA's Timestamp Doesn't Match the System Time
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
This can occur from one of two reasons:
First Scenario:
Timestamps shown in the JIRA UI don't match the user's timezone but that of the server location. The timezone used is a JVM system property which defaults - unless specified - to that of the hosting operating system
It is not possible to localize the timezone on a per-user basis. It is possible to change the JVM timezone by setting the following JVM command line property: -Duser.timezone=<TZ>. Possible values are in the zoneinfo format (please see this list of zoneinfo time zones).
To set a command line option, see Setting properties and options on startup.
Global organizations may consider setting the value to UTC.
Second Scenario:
JIRA's date/time may not have been updated after day light savings has taken affect - this is generally an issue with older versions of JAVA.
Upgrading JVM to the latest version will solve the problem. Please download the latest version from Java Download site.
For further reference, see the following document: