Daylight Saving Changes (Time zone issue)

This article is for Tempo for Cloud and Data Center

There are 2 possible reasons why the logged time of the worklogs are not showing correctly between Jira and Tempo.
Please note that it is an expected behaviour that Jira worklogs are showing with UTC time and Tempo worklogs are showing with local time. You can find more detailed explanation on our KB article: Why is there a time difference between my Jira worklog and my Tempo worklog? . If you try to disable/uninstall Tempo plugins, all these tabs (All, Comments, History, Activity, Worklogs, Transitions) in this "Activity" panel will remain the same. Since the "Activity" panel is a Jira feature, Tempo cannot modify it in any way, please contact Atlassian Support for more info. There is a common Jira issue every year, many Tempo customers have experienced it during daylight saving change period. Because the JVM needs to be changed by adding the argument -Duser.timezone=GMT-3 (as per your time zone) in JVM arguments for Jira, the problem will be resolved by adding this argument inside the JVM_SUPPPORT_RECOMMENDED_ARGS. If problem persists, please contact Atlassian Support for more help. Please make sure you have update your Java Runtime Environment if your region/country has recently stopped using Daylight Saving changes. Please refer to this article for more details: Time Zone Daylight Saving Changes and Java version \| Adjusting for daylight saving time .

There are 2 possible reasons why the logged time of the worklogs are not showing correctly between Jira and Tempo.

Please note that it is an expected behaviour that Jira worklogs are showing with UTC time and Tempo worklogs are showing with local time. You can find more detailed explanation on our KB article: Why is there a time difference between my Jira worklog and my Tempo worklog? . If you try to disable/uninstall Tempo plugins, all these tabs (All, Comments, History, Activity, Worklogs, Transitions) in this "Activity" panel will remain the same. Since the "Activity" panel is a Jira feature, Tempo cannot modify it in any way, please contact Atlassian Support for more info.
There is a common Jira issue every year, many Tempo customers have experienced it during daylight saving change period. Because the JVM needs to be changed by adding the argument -Duser.timezone=GMT-3 (as per your time zone) in JVM arguments for Jira, the problem will be resolved by adding this argument inside the JVM_SUPPPORT_RECOMMENDED_ARGS. If problem persists, please contact Atlassian Support for more help.
Please make sure you have update your Java Runtime Environment if your region/country has recently stopped using Daylight Saving changes. Please refer to this article for more details: Time Zone Daylight Saving Changes and Java version | Adjusting for daylight saving time .