Team Calendars for Confluence: Summer Time Bug for Recurring Tasks

Jiri Pik

If I set up a recurring task which starts every week at 0900 am and ends at 1000 am in June, in the winter, it will be starting at 1000am and ending at 1100am.

This is obviously wrong, not to mention that the starts of the summer time Confluence has may not be correct.

Is it possible to fix this?

Diego_88dj6o

Hello Jiri!

This is happening due to the fact that Team Calendars shows the events based on the user Timezone, not the internal calendar timezone.

This helps when users from different timezones use the same calendar. If You and I worked with a company from Sydney, both of us would be able to use the same Sydney calendar without the need of converting the events date and time for our own timezones.

The calendar also considers daylight saving times to display events to the users so the date and time are still the same for the internal calendar timezone (GMT+2, for example) and is updated for everyone else.

For example:

1. Our main office is in Sydney
2. All dates and events are based on Sydney's timezone
3. We have a meeting at 12PM Sydney every Monday
4. This will be marked as 11PM for me, in GMT-3
5. And will be marked as 4AM for GMT+2 (Daylight savings considered)

For short we can say that All events take in consideration the internal calendar timezone when scheduling and changing daylight savings.

Let us know if this clears things up for you Jiri!