Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341796 - keep "Tasks of interest" visible in focused task list without scheduling
Summary: keep "Tasks of interest" visible in focused task list without scheduling
Status: RESOLVED DUPLICATE of bug 168363
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: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 10:50 EDT by Thomas Ehrnhoefer CLA
Modified: 2011-04-05 14:01 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Ehrnhoefer CLA 2011-04-04 10:50:10 EDT
A very common use case for me is to have certain tasks, which are of some sort of interest that I want to see them in my focused task list (e.g. an ongoing task to manage a website editing lock, or a "collect questions" style task). Basically I know I have tasks I am opening those tasks rather frequently and don't want to search or need to unfocus the task list to do so.

Currently I am using "schedule for this week" to keep them in focus, but that's actually misusing this, especially since this way I can't really use the scheduling view. Scheduling should be done for tasks which actually need some work/attention at a certain point in time, whereas the tasks I am talking about here don't necessarily need work, but should be visible for other reasons. 

Not sure if this is just me, or others have those kind of tasks as well. If so, maybe we could have some sort of "Starred" category, and those starred tasks would show up in focused mode in all presentations and thus not clutter the "this week" list of tasks to work on.
Comment 1 Steffen Pingel CLA 2011-04-05 14:01:49 EDT
Thanks Thomas. Please add your requirements to bug 168363 if they are not already captured on the bug.

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