Bug 90008

Summary:	Reading mailed free busy information with KOrganizer fails to edit the fb information of the attendee into the event
Product:	[Applications] korganizer	Reporter:	Michel de la Giroday <michel>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	finex, tuju, vanmeeuwen
Priority:	NOR	Keywords:	needs_verification, triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Michel de la Giroday 2004-09-22 13:04:44 UTC

Version:           3.3 (proko2 branch) (using KDE 3.2.1, compiled sources)
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:                Linux (i686) release 2.4.21-243-default

Tested using Kontact as a KDE Kolab client - KDEPIM 3-3 branch / proko2 branch

First Make sure user2's KOrganizer does not Publish free busy information automatically.

as user1 create an event with yourself and user2 as attendees.
as user2 accept the invitation
as user1 enter the acceptation into your calendar.

as user1 edit the event and consult the Free Busy tab section.
At this point we can only read user1 (the owner) free busy information.

As user2 run Schedule->Mail Free Busy information and send it to user1
As user1 right click on the attached free busy message - Choose Open - Open with KOrganizer.
user1's view pass to Calendar view after a few seconds.
As user1 edit the event and consult the freebusy tab section.
We still dont have user2s free busy information.

we should....

Comment 1 Reinhold Kainhofer 2006-11-02 18:59:07 UTC

Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.

Comment 2 FiNeX 2008-11-24 15:25:24 UTC

Someone with a kolab server should try using new korganizer/kolab server.

Comment 3 Jeroen van Meeuwen (Kolab Systems) 2012-06-08 13:31:08 UTC

RESOLVED / WAITINGFORINFO as no feedback has been generated on this issue for 3 years and then some. Feel free to reopen this issue with the appropriate feedback, if at all necessary.