After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 230060 - Evolution mishandles recurring events
Evolution mishandles recurring events
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal major
: ---
Assigned To: Rodrigo Moya
Evolution QA team
evolution[connector]
: 221868 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-09-09 15:00 UTC by Dan Winship
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dan Winship 2002-09-09 15:00:10 UTC 
Evolution expects every exception to a recurring meeting to have its
own UID. RFC2445 is vague on this, but the consensus on the ietf-calendar
list is that this is wrong: the recurring event as a whole has a UID,
but individual instances and exceptions all share that same UID and just
have different RECURRENCE-IDs. That's how Exchange works, and this
causes problems between Evolution and Outlook/Exchange.
Comment 1 Dan Winship 2002-09-09 15:00:43 UTC 
*** http://bugzilla.ximian.com/show_bug.cgi?id=27212 has been marked as a duplicate of this bug. ***
Comment 2 Dan Winship 2002-09-09 15:00:58 UTC 
*** bug 221868 has been marked as a duplicate of this bug. ***
Comment 3 Dan Winship 2002-09-09 15:01:14 UTC 
*** http://bugzilla.ximian.com/show_bug.cgi?id=28009 has been marked as a duplicate of this bug. ***
Comment 4 Hans Petter Jansson 2003-03-05 19:59:17 UTC 
According to JP's analysis, there's no time to do this for 1.4.
Architectural changes will go into 1.6.
Comment 5 Gerardo Marin 2003-11-28 20:11:52 UTC 
1.5.2 milestone then.
Comment 6 Rodrigo Moya 2004-03-15 11:07:54 UTC 
I think most stuff should be fixed now. Dan, could you tell me what
exactly you are missing?
Comment 7 Dan Winship 2004-03-15 15:24:24 UTC 
Well, here are the things it should be possible to do:

  - create a recurring meeting
  - remove a single instance of a recurring meeting
  - move a single instance of a recurring meeting and still have
    that instance be associated with the original meeting (meaning
    that if you delete "all occurrences" of the meeting, the moved
    one gets deleted too)
  - (in theory, you should be able to add instances too, but we
    don't have ui for this)
  - move or delete a previously moved instance
  - move or delete all past or future instances of a meeting
    (which should do something (???) with exceptions in that range)

  - send a meeting request that does each of the above
  - receive a meeting request that does each of the above
Comment 8 Rodrigo Moya 2005-01-12 13:59:31 UTC 
All this should be now possible, please add individual bugs for the
things that might be missing.