Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347422 - Click on "new" / "incoming" marker in Task List should mark task as read
Summary: Click on "new" / "incoming" marker in Task List should mark task as read
Status: RESOLVED DUPLICATE of bug 342928
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 211011
  Show dependency tree
 
Reported: 2011-05-27 05:26 EDT by Jörg Thönnes CLA
Modified: 2011-08-29 20:47 EDT (History)
3 users (show)

See Also:

Attachments
Screen shot showing where to click (4.85 KB, image/png)
2011-05-27 05:28 EDT, Jörg Thönnes 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 Jörg Thönnes CLA 2011-05-27 05:26:10 EDT 
If the notification with new tasks or incoming changes pops up, I can click on the "new" or "incoming" marker icon
to mark it read.

This would be also nice for the Task List few: Click on "new" / "incoming" marker to mark it as read.

h1. Versions

bc. 
-- Configuration Details --
Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.mylyn_feature 3.5.1.v20110422-0200
Comment 1 Jörg Thönnes CLA 2011-05-27 05:28:01 EDT 
Created attachment 196732 [details]
Screen shot showing where to click
Comment 2 Steffen Pingel CLA 2011-08-11 10:04:06 EDT 
I like the idea. I am a bit concerned though that it would be too easy to click incoming arrows accidentally. We still lack proper undo support making it difficult to recover. Any other thoughts?
Comment 3 Sam Davis CLA 2011-08-29 20:14:30 EDT 
Isn't this a duplicate of bug 342928?
Comment 4 Steffen Pingel CLA 2011-08-29 20:47:07 EDT 
Thanks! I had the odd feeling that there was a duplicate somewhere but couldn't find it.

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