GNOME Bugzilla – Bug 264682
Moving a appts from one calendar to another sends update
Last modified: 2006-04-12 10:34:31 UTC
I have a bunch of appointents that were on my Personal calendar, and I moved them to my Groupwise calendar. Even if I don't own the appt. (i.e. - Charlie Ungashick sent the meeting in the first place) all the attendees get an e-mail saying the meeting has moved. For one, it hasn't changed at all for the attendees. It has just changed which calendar I have it on. Two, I shouldn't be sending out updates to appointments I don't own. # rpm -qa | grep evolution evolution-1.5.93.0.200408270830-0.snap.ximian.0.1 evolution-data-server-0.0.98.0.200408270830-0.snap.ximian.0.1
If the user wants to post the appt from a personal calendar to a GroupWise calendar, a new SOAP method needs to be used: createItemRequest(). This will post the item to the users GroupWise calendar without doing a send to other users.
A couple more things regarding the createItemRequest. It will create the item in the SentItems folder by default. If the sender is sending the item only to him/her self, then a <source>personal</source> is required. If you are sending to other users only, <source>sent</source> for the item. This means the item will only appear in the sentItems folder. If you are sending to yourself and other users, <source>received</source> will create the item in the inbox. Sending more info to Chen.
When the Item is Created using a CreateItemsRequest while moving from the Persoanl calendar to groupwise the <from> element changes when the Item is retried back from the server. The backend identifies only the Organizer only from the <from> element. Have reported the problem to tim.
Should have a server fix for this today (10/12). Should this be in 6.5.3?
Added fix for <from> or organizer not getting added correctly. This is in Seq and GW653
Can we close this out?
Well... I have moved appts from my personal to GW calendar (when access to GW cal is working) and no one has complained that they received updates. Has QA looked at this?
committed the fix to gnome-2-8 branch and head.
replicable in evo 2.0.4 using an exchange account. reopening bug.
Is it only an Exchange Calendar bug now?
no such behaviour now