-
Bug
-
Resolution: Timed out
-
Low
-
None
-
4
-
Severity 3 - Minor
-
Issue Summary
The GMT offset shown in the "Personal settings" page does not account for "summer" or "daylight savings" time:
Steps to Reproduce
- Navigate to the Personal profile settings: https://<instance>.atlassian.net/secure/ViewPersonalSettings.jspa
- 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
[ID-7125] Personal settings: GMT offsets for Americas and European timezone do not account for "summer" or "daylight" timezones
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| Support reference count | Original: 1 | New: 2 |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
This screen is Unified Profile, which is owned by People and Teams
| Resolution | Original: Won't Fix [ 2 ] | |
| Status | Original: Closed [ 6 ] | New: Needs Triage [ 10030 ] |
| Component/s | New: Atlassian account profile details [ 56705 ] | |
| Component/s | Original: User Management [ 46556 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Jira Cloud (including JIRA Core) [ 18514 ] | New: Identity [ 16810 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 3343044 ] | New: JAC Bug Workflow v3 [ 3362555 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
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