-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Severity 3 - Minor
-
Summary
Checking out time zones it appears our tz database is out of date. This can be seen as the new permanant change for Casablanca to GMT+1 is not reflected.
Environment
Jira - Production
Steps to Reproduce
- Go to https://id.atlassian.com/manage-profile
- Browse for Casablanca Timezone in Location and time zone section
Expected Results
Casablanca timezone should be GMT+1
Actual Results
Casablanca timezone is GMT+0
Notes
I have downloaded the latest tz database and checked, it appears this indeed been implemented in the tz database.
# Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26 0:00 Morocco +00/+01 1984 Mar 16 1:00 - +01 1986 0:00 Morocco +00/+01 2018 Oct 28 3:00 1:00 Morocco +01/+00
It seems we need to run the Oracle Timezone Updater Tool.
Workaround
None
Hi everyone,
Thank you for raising and following this bug report. Because there have been no new reports of this issue over the last year, we are closing this ticket as "Timed Out". If this bug is still impacting your team, please let us know in a comment on the ticket. Thanks again for continuing to provide valuable feedback to our team.