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

Bug 193575

Summary:	New issues opened via Mylyn UI shouldn't appear as new items when synchronizing first time
Product:	z_Archived	Reporter:	Andreas Goetz <cpuidle>
Component:	Mylyn	Assignee:	Robert Elves <robert.elves>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Andreas Goetz

2007-06-20 13:13:54 EDT

Not sure if this is possible as it requires some assumptions about the task repository, but: when I open a new issue using the Mylyn UI, I usually don't want to see the inbound sync into the repository as new information- as it simply isn't. I would only be interested once the first comments have been added or the attibutes have changed.

Comment 1 Andreas Goetz

2007-09-25 05:16:41 EDT

Hi Mik, Eugene,
this was apparently never reviewed- any comment?

Comment 2 Eugene Kuleshov

2007-09-25 10:32:43 EDT

It been moved to Rob's department, but haven't been prioritized.

Comment 3 Robert Elves

2007-09-25 10:48:56 EDT

I'm not sure I completely understand the request. Andreas, could you expound on this?

Comment 4 Andreas Goetz

2007-09-25 12:10:16 EDT

When I open a bug using Mylyn, I notice that it appears as new and unread in the task list (or did with 2.0, didn't re-check with 2.1)- same as if I opened via browser. Difference is that Mylyn knows that I opened and wrote that bug and shouldn't necessary need my attention for reading it again. When opening on the web, Mylyn in contrast can't know that I opened the bug and know about it already?

Comment 5 Robert Elves

2007-09-25 17:16:37 EDT

Sounds like you are seeing the false incoming behavior which result from the time stamp changes due to Eclipse.org upgrading to Bugzilla 3.0  (See bug#198714)

Comment 6 Andreas Goetz

2007-09-25 17:54:41 EDT

Quite possible. Wouldn't know how to test though. Resolving as WONTFIX for now. Thanks!

Comment 7 Robert Elves

2007-09-25 18:04:34 EDT

To work around this you can select all tasks from your eclipse.org queries and select synchronize from the context menu.  Then those with false incoming can be reviewed in one pass. Once these tasks have gone through this 'false' incoming state upon opening it in the future you shouldn't get the false incoming.

Comment 8 Robert Elves

2007-09-25 18:04:47 EDT


*** This bug has been marked as a duplicate of bug 198714 ***