Issue Summary

Users in non-canonicalized timezones may receive a warning banner when creating/starting a sprint:

Your local timezone ({}) doesn't match your Jira profile timezone ({}). We recommend changing the profile timezone so that it becomes the same as the local one. Meanwhile, your profile timezone is used in the sprint start date and end date.

This occurs because there's a mismatch between the user's Jira profile timezone and their browser-provided timezone. For this bug report, the mismatch is between two identifiers pointing to the same UTC offset.

Jira and browsers use IANA tz database identifiers, but Jira always uses canonical names. Chrome, Edge, and Safari instead provide a link (non-canonical) timezone. Firefox is the only browser known to always provide the canonical timezone. There is a Chromium bug and JavaScript proposal to standardize this, but neither has been implemented yet:

1. Asia/Calcutta Timezone Identifier should be replaced by Asia/Kolkata
2. TC39 Proposal

You can confirm your browser's timezone by executing the following from the development tools' JavaScript console:

Intl.DateTimeFormat().resolvedOptions().timeZone

Steps to Reproduce

1. Set OS timezone to Asia/Kolkata (UTC+05:30).
2. Set Jira user profile timezone to Asia/Kolkata.
3. Navigate to a software project backlog using Chrome/Edge/Safari.
4. Try to create a sprint.
5. Or Prepare a sprint and select start sprint.

Expected Results

No warning appears in the "start sprint" dialog.

Actual Results

A warning banner appears in the dialog:

Your local timezone (Asia/Calcutta) doesn't match your Jira profile timezone (Asia/Kolkata). We recommend changing the profile timezone so that it becomes the same as the local one. Meanwhile, your profile timezone is used in the sprint start date and end date.

Workaround

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