JIRA Issue Calendar Gadget timezone unconformity

Summary

When the user uses the JIRA Issue Calendar gadget, provided by the JIRA Calendar Plugin, it's possible to have a timezone unconformity when configuring the gadget with a DateField portlet.issuescalendar.field.dateFieldName.name set with the Created or Updated fields. These fields record timezone related information, and the gadget uses the JIRA`s Server system timezone instead of the Default user timezone or the User Preference Timezone (set by the user on his profile configuration). This is a problem when the JIRA's server system timezone is enough hours ahead of the user profile timezone that makes a few issues created on a specific day appear on the next day slot on the JIRA Issue Calendar gadget.

I.e.: JIRA's server system timezone: GMT and the User profile preference timezone: GMT -8. The user created an issue on October 3rd around 6PM PST, but the gadget shows the issue on the October 4th slot at 2AM since it adjusts to the server time instead of the user preference time.

Date fields that have no time component, such as due dates, release dates (associated with versions) and custom date fields, solely record date information (and no time zone-related information) so are not affected by time zone settings. So if the gadget is configured to use the due date field, the issues appear using the user profile preference timezone correctly.

Problem

If JIRA's server system timezone is enough hours ahead of the user profile timezone that makes a few issues created on a specific day appear on the next day slot on the JIRA Issue Calendar gadget when the gadget is configured to use the Created or Updates DateFields.

Cause

JIRA is using JIRA Server system timezone instead of JIRA User profile preferences timezone or JIRA Default user timezone (configured by the administrator) when the gadget is configured to use the Created or Updates DateFields.

Workaround

• If it's possible, configure the gadget using the due date DateField configuration instead of any other field, and then configure JIRA user default timezone and the JIRA Profile Preferences timezone (for each user) to Los Angeles. The gadget will behave correctly.

• Or, if it's possible, the user can set the timezone for the Java environment on the setenv.sh file, forcing the system to use this timezone instead of the JIRA's server system timezone, although a few other problems might appear so be careful when changing this configuration.

https://confluence.atlassian.com/kb/setting-the-timezone-for-the-java-environment-841187402.html