Bug 135774

Summary: The "Apply to All" appointment option doesn't work within evolution.
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Joe Harmon <jharmon>
Component: EvolutionAssignee: Harish Krishnaswamy <kharish>
Status: VERIFIED FIXED QA Contact: Poornima Nayak <pnayak>
Severity: Critical    
Priority: P5 - None    
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Joe Harmon 2005-11-28 23:33:15 UTC
When I receive reaccuring appointments in evolution, there is an "Apply to All" that will allow you to accept or decline multiple appointments as once. However, when I receive appointments and check that option, the accept all doesn't appear to work. I still have to accept each appointment individually.
Comment 1 Harish Krishnaswamy 2005-12-01 17:42:54 UTC
I assume you did not see any error messages since you have not mentioned any. Are there any related warnings on the EDS console ? Could you provide the EDS traces with GROUPWISE_DEBUG=1 set. A similar bug had been fixed long ago and this is not known (well, not until this bug at least) to occur in the subsequent builds.
Comment 2 Joe Harmon 2005-12-01 17:51:23 UTC
(In reply to comment #1)
> I assume you did not see any error messages since you have not mentioned any.

That's correct. It accepts the existing apointment, but the rest of the appointment are still in the inbox.

> Are there any related warnings on the EDS console ? Could you provide the EDS
> traces with GROUPWISE_DEBUG=1 set. A similar bug had been fixed long ago and
> this is not known (well, not until this bug at least) to occur in the
> subsequent builds.

I will have to send myself some concuring appointments and then setup for a SOAP trace.

Comment 3 Joe Harmon 2005-12-01 18:02:05 UTC
Ok, I went into the Groupwise client and sent me 5 reaccuring appointments. I then went into evolution and checked the "Apply to All Instances" option and then choose accept. It still only accepted one appointment. Here is the trace.

SOAP-Debug: 0x48945fd0 @ 1133460072
Pragma: no-cache
Date: Thu, 01 Dec 2005 10:58:48 GMT
Server: Windows NT GroupWise POA 7.0
Content-Length: 536
Content-Type: text/xml

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header SOAP-ENV:encodingStyle=""/><SOAP-ENV:Body SOAP-ENV:encodingStyle="" xmlns:types="http://schemas.novell.com/2003/10/NCSP/types.xsd"><destroyCursorResponse><status><code>0</code></status></destroyCursorResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
** Message: Response 1
** Message: Number of attachments is 0
** Message: Deleting!
Comment 4 Joe Harmon 2005-12-01 18:06:45 UTC
hmmm, interesting. I went to put this information in the bug, and then went back into evolution after a few minutes. The other appointments are no longer in the inbox. Perhaps it is a timing issue. I then went into the calendar and I can see the appointments I accepted if I look at each day in the "day" view. If I look at the "work week" view then I only see one appointment.
Comment 5 Joe Harmon 2005-12-01 18:12:51 UTC
It shows the individual appointment that I accepted in every view. The other appointments only show in only the individual day view.
Comment 6 Harish Krishnaswamy 2005-12-12 08:15:14 UTC
Joe, sorry for the late comment. I had thought I had replied back to this comment - but noticed just today that it had never got saved.

Thanks for trying this out. I verified that while the functionality of accepting multiple appointments is working fine - there are random issues in Week/Month/list views (also depends on the server you are hitting) which have been fixed in 2.5.x but not available on 2.4.x.

Chen, could we explore having the fix in 2.4.x too ?
Comment 7 Forgotten User ex4EZfzxBL 2005-12-14 12:02:53 UTC
This fix needed an API change and is available in 2.5.x. Since its break API it caannot be taken for 2.4.x.