Jira doesn't account for Mexico's daylight savings time changes

Issue Summary

As of Oct 30, 2022, daylight savings time (DST) is no longer observed in Mexico. Previously, DST began the first Sunday of April and ended the last Sunday of October. Instances using a Mexico TZ identifier (Area/Location) will exhibit inconsistent timezone behavior throughout the application.

The system info page (⚙️ (gear icon) > System > System info) displays the correct UTC offset and system time. However, timestamps are one hour ahead in other areas of Jira's interface.

Technical explanation

The timestamps in the created/updated date block, comments, and many other UI components use the joda-time library to format timestamps (com.atlassian.jira.datetime.DateTimeFormatter#format). Jira has used joda-time 2.10.5 since at least 8.20.

As stated in an ICANN announcement, Mexico's DST change is first accounted for in tzdata2022f. According to the joda-time Release History, TZ data was updated to 2022f in version 2.12.1 (2022-10-29).

This is reproducible on Data Center: yes

Steps to Reproduce

1. Set the Duser.timezone JVM arg to America/Mexico_City.
2. Restart Jira.
3. Set the default user time zone (jira.default.timezone) on the general configuration page to system default.
4. Ensure the current Jira user is using the Jira default timezone.
5. Create a new issue.

Expected Results

The issue created/updated time matches the current UTC−06:00 time.

Actual Results

The created/updated times are one hour ahead (UTC−05:00).

Workaround

Set the default user time zone setting (or Duser.timezone JVM arg) to another region with the same UTC offset that doesn't observe DST, such as Guatamala for UTC-06:00.