Bugzilla – Full Text Bug Listing
| Summary: | [discussion] Make it easy to build up the context for new tasks | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Michael Scharf <eclipse> |
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | sflaniga, wmitsuda |
| Version: | unspecified | ||
| Target Milestone: | 3.0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | http://www.scharf.gr/eclipse/Probmens/Mylar/ContextProblem/ | ||
| Whiteboard: | |||
|
Description
Michael Scharf
To me it seems that copying current context into new task (e.g. when new task created while some other task is active) does make sense and also quite natural. All other suggested options seem way too specific to this workflow... Copying context from one task to another sounds good to me. However, rather than always copying an active context, it would be better to add a new action: Clone Task. Always copying the context is probably not the right thing. I think a button for option "2" (er, the first "2": keeping editors open) would be useful as well. I often forget to deactivate the current task before following a rabbit trail. When I remember, I would like to deactivate the task (to avoid polluting the context) but keep working in those editors. If I had to choose just one, I think I would take the latter. Within a few weeks we should have the copy/paste context functionality to experiment with. Once we all get some experience with that let's use this bug to discuss improving the workflow. sounds good :-) I also use Mylar extensively and have had this problem. Personally, solution #3 seems like it would make the most sense, but I have the following suggestion: - If I create a new task when there is another task already open, Mylar could prompt me if I want my task context from the current task copied into the new task. I sometimes bulk-add tasks one after the other, forgetting to close the current task. It would be just as annoying to go to the other tasks later to find that they had copied the (irrelevant) context of the open task. If I create a task with no existing task open, then Mylar wouldn't prompt me. So it would be easy to get rid of the prompt--just deactivate the current task, add the new ones, then reactivate the current task. Michael: are you now using the copy/paste context to work around this? If so how is it working? The idea with adding that was to get people to experiment with it, since in one way or another all of your suggestions are related to copying context. We usually out what the right automation/streamlining is to add the manual support and get feedback on that. We could do some of what you and Dave are suggesting, but need to make sure this kind of context copying is the right way of "forking" the kinds of tasks that you describe, especially sine we're also considering what to do with subtasks and contexts (bug 137543). Btw, regarding the steps in your video, note that all of the editors that were closed are still in your "Back" list on the toolbar. This is essential, because no matter what Mylar is doing with the context the navigation history persists, meaning that the last 10 open editors can always be opened. Need to hear back on comment#6 to investigate further. We have had very little feedback from users about using the "Copy Context To" functionality. However, this is still an open problem in 3.0 and bug 196751 might be helpful in providing a good 'seed' context when first activating a task. For 3.0 the idea is to custom draw facilities in views that are filtered when there is no context active, so that the view can still be navigated without being unfiltered. *** This bug has been marked as a duplicate of bug 172580 *** |