Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360737

Summary: Decision Meeting Update shall populate existing information
Product: z_Archived Reporter: Alvaro Sanchez-Leon <alvaro.sanchez-leon>
Component: MylynAssignee: Sebastien Dubois <sebastien.dubois>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: lmcbout
Version: unspecified   
Target Milestone: 0.9   
Hardware: All   
OS: All   
Whiteboard:

Description Alvaro Sanchez-Leon CLA 2011-10-12 17:25:59 EDT 
if the update button of an existing meeting is pressed, 
the values populated in the Meeting are the default values, rather than the current values.  
This reflects the creation of a new meeting every time.

This is in fact not desirable for e.g an Outlook connector as the meeting has an id and can be used to in fact open up the meeting instance and update it directly without the need to multiply different meeting instance which need to be manually tracked.

for Linux, there is no unique id that can be used as there are multiple mail solutions, but at the update calendar dialogue should at least reflect the current values.
Comment 1 Sebastien Dubois CLA 2011-10-13 17:08:36 EDT 
After some investigation, I realized that there is a problem with the Outlook connector that does not retrieve the existing Meeting information properly.

Nonetheless I updated the code to support re-using existing meeting requests if possible instead of creating new ones.  For SMTP, I also updated the code to have the last meeting request values by default when updating it.
Comment 2 Sebastien Dubois CLA 2011-10-13 17:16:09 EDT 
This bug is depends on bug 360250 and internal bug 902 for full resolution
Comment 3 Sebastien Dubois CLA 2011-10-14 14:22:02 EDT 
Added fixed for Refresh and Update buttons.  Also fixed a bug in internal Outlook connector where the meeting start time was not fetched properly
Comment 4 Sebastien Dubois CLA 2011-10-19 16:54:29 EDT 
internal bug 902 closed as it was due to a corrupted file
Comment 5 Sebastien Dubois CLA 2012-02-22 16:39:10 EST 
This bug is fixed as of Feb 22nd 2012