-
Bug
-
Resolution: Fixed
-
High
-
None
-
21
-
Severity 3 - Minor
-
Issue Summary
- Users are reporting that their their time-zone has been set to GMT 0 (UTC) in product like Confluencne.
- Checking further, it appears that their time-zone values have been set to blank in their profile.
Steps to Reproduce
- Check the user's time-zone in product like Confluence, and it would be set to "GMT+0000".
- https://<SITE-NAME>.atlassian.net/wiki/users/viewmysettings.action
- Check the account preferences, and the time-zone field is blank.
- https://id.atlassian.com/manage-profile/account-preferences
- This causes issues with apps the rely on the time-zone, like Team Calendar.
- There's another bug for Team Calendar where it caches the time-zone value, and it takes awhile for the time-zone changes to be picked up by Team Calendar.
- There's also the issue that the daily and weekly update emails are using the UTC time-zone for edit times.
Expected Results
- Customer time-zone values should be set to their correct time-zones that they've set before.
Actual Results
- Customer's time-zone has been updated to blank values.
Workaround
- Manually update the time-zone in account preference.
- is related to
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[ID-7800] User's time-zone being set to blank and defaulting to UTC (GMT 0) in product
| Remote Link | New: This issue links to "Page (Confluence)" [ 599142 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 598568 ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 580013 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Support reference count | Original: 20 | New: 21 |
| Status | Original: Short Term Backlog [ 12074 ] | New: In Progress [ 3 ] |
| Assignee | New: Del [ dneo ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 592146 ] |
| Support reference count | Original: 19 | New: 20 |
smaran I am resolving this now as the issue on the Identity side is fixed and only supported timezones are now returned to callers. Users who had an invalid timezone stored for them will need to update their profile and reselect a timezone.
Product behaviour on what happens when a user has no timezone is external to identity. If there are any issues with what the defaulting behaviour is, it should be raised with the respective product teams as timezone is optional and new users don't get created with one by default.