Uploaded image for project: 'Identity'
  1. Identity
  2. ID-7125

Personal settings: GMT offsets for Americas and European timezone do not account for "summer" or "daylight" timezones

XMLWordPrintable

      Issue Summary

      The GMT offset shown in the "Personal settings" page does not account for "summer" or "daylight savings" time:

      Steps to Reproduce

      1. Navigate to the Personal profile settings: https://<instance>.atlassian.net/secure/ViewPersonalSettings.jspa
      2. Try to change the timezone settings by selecting the city that you'd like to set the timezone setting to

      Expected Results

      The GMT offset is correct given the time of year

      Actual Results

      The GMT offset is usually behind by 1 hour as the field values do not account for "summer" or "daylight savings" time.

      Notes

      • Important to note that the timezone is set correctly and the timestamps in Jira are displaying the correct local time. It's only the GMT offset values in the settings page that is not correct
      • Loosely related to JRACLOUD-70089

      Workaround

      • No known workarounds to get the GMT offset information to display correctly
      • The timezone settings can still be selected by city

        1. Screenshot 2019-08-13 at 10.36.10.png
          Screenshot 2019-08-13 at 10.36.10.png
          166 kB

            [ID-7125] Personal settings: GMT offsets for Americas and European timezone do not account for "summer" or "daylight" timezones

            Kat N added a comment -
            Atlassian Update – 15 Dec 2020

            Hi everyone,

            Thanks for raising and following this issue. Because there's been no user engagement (votes, watches, comments) over the last year, we have no plans to implement this in the foreseeable future. In order to set expectations, we're closing this request to focus on our upcoming roadmap.

            If you still feel that this issue significantly impacts your team, please let us know on the ticket. Thanks again for continuing to provide valuable feedback to our team.

            Regards,
            The Identity PM team

            Kat N added a comment - Atlassian Update – 15 Dec 2020 Hi everyone, Thanks for raising and following this issue. Because there's been no user engagement (votes, watches, comments) over the last year, we have no plans to implement this in the foreseeable future. In order to set expectations, we're closing this request to focus on our upcoming roadmap. If you still feel that this issue significantly impacts your team, please let us know on the ticket. Thanks again for continuing to provide valuable feedback to our team. Regards, The Identity PM team

            undefined (Inactive) added a comment -

            This screen is Unified Profile, which is owned by People and Teams

            undefined (Inactive) added a comment - This screen is Unified Profile, which is owned by People and Teams

            Peter Weinberger added a comment -

            Timezones will be set by id.atlassian.com and not in Jira going forward. Given that, this won't be fixed in the short term by Jira.

            Peter Weinberger added a comment - Timezones will be set by id.atlassian.com and not in Jira going forward. Given that, this won't be fixed in the short term by Jira.

              Unassigned Unassigned
              dnguyen4 Derrick Nguyen
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: