Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323190 - tasks with shared due dates are not always correctly migrated
Summary: tasks with shared due dates are not always correctly migrated
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.4.2   Edit
Assignee: Shawn Minto CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 301315 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-19 16:17 EDT by Shawn Minto CLA
Modified: 2010-11-28 16:13 EST (History)
2 users (show)

See Also:

Attachments
patch (4.06 KB, patch)
2010-08-19 16:36 EDT, Shawn Minto CLA 		no flags Details | Diff
mylyn/context/zip (807 bytes, application/octet-stream)
2010-08-19 16:36 EDT, Shawn Minto CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn Minto CLA 2010-08-19 16:17:51 EDT 
If a connector supports shared due dates and stores it on the task data (not the task), when the new task is submitted, the due date is correct in the repository, but the TaskMigrator moves the due date from the local task object to the new repository task object.  This results in the repository task looking like it has no due date until the next time that it is synchronized.
Comment 1 Shawn Minto CLA 2010-08-19 16:36:41 EDT 
Created attachment 177046 [details]
patch

To fix this, I added a flag to the TaskMigrator as to whether to migrate the due date from the local task or not.  I will commit this patch to the branch and to HEAD.
Comment 2 Shawn Minto CLA 2010-08-19 16:36:42 EDT 
Created attachment 177047 [details]
mylyn/context/zip
Comment 3 Shawn Minto CLA 2010-08-19 16:39:29 EDT 
Patch applied to both the branch and to HEAD.
Comment 4 Shawn Minto CLA 2010-11-28 16:13:35 EST 
*** Bug 301315 has been marked as a duplicate of this bug. ***