Franco Skrzypczak

I am seeing this for the first time in Confluence 7.17 with events that are pulled from Jira 8.22. System timezone is GMT but the user had theirs set to Azures. Oddly setting to Cape Verde which is the same offset cleared the problem but I just told them to use the default system timezone.

A fix for this issue is available to Server and Data Center customers in Confluence 7.12.0
Upgrade now or check out the Release Notes to see what other issues are resolved.

The timezone definitions in Confluence Server/Data Centre are currently outdated, this will be fixed in Confluence 7.12.

This issue affects timezones where the clock is moved forward an hour at 0:00am. Brazil abolished DST in 2019 and in Confluence 7.12 you will not face this bug with events created on days since 2019.

Hi support237,
I cannot see the screenshot that you have attached. I am unable to reproduce this bug as described in the original ticket. Could you please provide more details about the event that you are trying to create and share the error message again?

Edit: I can reproduce this issue when creating all day events on days where DST changes. For example 21/10/2018 for Brazil. Is that the issue you were facing?

Regards,
Alex K (Developer at Atlassian)

Well, I am facing this issue as well.

Confluence version: 6.15.12

Team calendar version: 6.1.1

System timezone: GMT

User Timezone: Time zone(GMT-0300) Brasilia

Hello,

I had the same issue, but it seems to be caused by events that starts at 00:00h of Oct/15/2017 (because of the skip from 23:59 to 01:00). I haven't tested events ending at 00:00 of Oct/15/2017, but it might be the same.

Multi-days events passing by 00:00 of Oct/15/2017 seem to be ok (e.g. an event from Oct/14/2017 to Oct/16/2017).

In my case, there was an "All Day" event on Oct/15/2017 (which started at 00:00h). After removing this event the calendar was shown without issues.

Confluence version: 5.10.7

Team calendar version: 5.3.19

System timezone: America/Sao_Paulo

User timezone: Site Default ((GMT-0300) Brasilia)

I am also seeing this in Confluence 6.1.1 and Team Calendars 5.3.20

Hello!

I tried to follow the above procedure, but it did not work.
Here is the workaround I did and it worked:

1. I stopped the service: systemctl stop confluence
2. I changed the time zone parameter in JAVA_OPTS through the /opt/atlassian/confluence/bin/catalina.sh file:
   -Duser.timezone=America/Buenos_Aires
3. I started the service: systemctl start confluence

Hi,

The original issue is happening again:

Version: Confluence 5.10.6
Team Calendars version: 5.3.15
Timezone for Calendar: Brazil/East (-0300)

Brazilian users cannot view the calendar.  Error message is:

Unable to load events of Deadlines (697....5): Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2017-10-15T00:00:00.000 (America/Sao_Paulo)

Is it also happening in Confluence 6?

I believe that classifying this as Minor priority is not in line with the priority descriptions published at: https://jira.atlassian.com/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels and the original bug was also marked as Major. Our entire Sao Paulo office literally can not use the product.

The workaround requires everyone in the office to manually and individually change their time zone settings at least twice. Editing the calendar time zone does not help.

Workaround to this issue:

• User goes to their profile page
• Click on Settings
• Clicks on the Edit button
• Sets their timezone to (GMT-300) Buenos Aires, Georgetown
• Save and verify that calendars are now accessible

 This will only work till Oct 16th because Buenos Aires does not change for DST, but Sao Paulo does. After Oct 16th, the time will be off by 1 hour.

We reproduced this with Confluence 5.8.18 and Team Calendars 5.3.11