Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 196602 - Be able to create a task from a "anonymous" context
Summary: Be able to create a task from a "anonymous" context
Status: RESOLVED DUPLICATE of bug 146125
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-16 01:20 EDT by Willian Mitsuda CLA
Modified: 2007-07-17 19:55 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 Willian Mitsuda CLA 2007-07-16 01:20:56 EDT
I'm not sure if this was discussed before, but anyway:

Mylyn workflow forces you to:

1 - Create a task.
2 - Work on it.

But many times I caught myself doing some work, so only then I figure out that it could be interesting turning it into a task.

For example:

- Navigate through news on live.eclipse.org and found some demo/tutorial.
- I think: "cool, I think I'll try on my machine".
- Start working, and after some time I think: "It is time to <do-another-thing>. I'll continue later".
- Then: "Ops! It would be good if I had created a task for this before".

My idea is:

- If there is no active task, collect interaction into some kind of "anonymous context".
- When you create a new task, offer the option to initially populate it with this "anonymous context".

So the workflow could be:

[ 1 - Do some work. ]
2 - Create a task [ populating the context with previous work ].
3 - Work on it.
Comment 1 Eugene Kuleshov CLA 2007-07-16 01:38:04 EDT
It is probably the same as create task context from the event log since last task deactivation. It would be a great feature.
Comment 2 Mik Kersten CLA 2007-07-17 19:55:58 EDT
Willian: please consider adding some of the details from your description that are not already covered on bug 146125 to that bug.

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