Google Calendar showing appointments early

Bug #786322 reported by Craig Maloney
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Confirmed
Undecided
Unassigned

Bug Description

We have set up an event as happening from 7p-10pm EDT EDT, but according to Google Calendar, the event is happening from 3pm-6pm.

http://loco.ubuntu.com/events/team/962/detail/ shows the event correctly for the right time zone.

The way that Google calendar is showing this event is from 3-6PM Eastern, but the iCal feed:

http://loco.ubuntu.com/teams/ubuntu-michigan/ical

has the following:

BEGIN:VEVENT
UID:962
DTSTART:20110525T230000
DTEND:20110526T020000
CATEGORIES:Ubuntu Loco Team Event
DESCRIPTION:the MI Loco teams up with the CoffeeHouseCoders team to hold a
  weekly geek meeting at a local coffee shop. For event details and mapping
  see: http://coffeehousecode.appspot.com/locations/detroit.html
SUMMARY:UH:CHC (Ubuntu Hour/Coffee House Coders)
END:VEVENT

I'm not sure what's going on to make Google calendar not arrive at the right time, but it's preventing us from moving to the Ubuntu calendar exclusively.

Tags: ical
Revision history for this message
Craig Maloney (craig-decafbad) wrote :

Note: This was originally brought up under https://bugs.launchpad.net/loco-directory/+bug/610416, but I was asked to enter a separate bug. Please refrain from marking this as a duplicate of that bug. Thanks!

Changed in loco-directory:
status: New → Confirmed
Revision history for this message
Jared Norris (jarednorris) wrote :

I actually hadn't noticed this issue until the latest release of the team portal/directory. Is it possible this issue was fixed and then has regressed in the last update? It's currently showing all ical entries 2 hours earlier than they should be according to the event.

Adnane Belmadiaf (daker)
tags: added: ical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.