Community
Participate
Working Groups
If a task that is not in the task list is opened from a search result the task editor does not indicate that the task is not in the task list. Suggestions for improvements: - Contribute an icon to the header toolbar for adding the task to the task list. - When the task is activated, display a message in the header of the task editor that prompts the user to add the task to the task list. - Show an information message in the header when the task is opened.
Sounds about right to me. Here's another pass: 1) A toolbar button that shows the Task List icon and a "+" overlay allows the user to add the task to the Task List. Behavior is that a dialog pops up, suggests that the user expand a query instead. If the user accepts the dialog, the task is added to the Unmatched container. 2) If the user tries to activate, they are first prompted with (1). I don't think that we should support activation of tasks that are not in the Task List unless we have a strong use case. 3) Information message can be: "Not in in " + TaskListView.getName() + ", click here to add"
> 2) If the user tries to activate, they are first prompted with (1). I don't > think that we should support activation of tasks that are not in the Task List > unless we have a strong use case. I agree. The same should apply to scheduling a task. I am okay with automatically adding the task to Uncategorized which seems less invasive than a dialog.
(In reply to comment #2) > I am okay with > automatically adding the task to Uncategorized which seems less invasive than a > dialog. +1. I assume that without the dialog, this means that we'll disable the Activate button?
I would like to keep the enabled activation button. The only change would be that activating a task that is not in the task list would automatically add it to the Uncategorized category.
There are some bad implications for having the button enabled, arising from the fact that the Task List is the canonical source of all tasks that the user has worked on. For example, facilities such as the task activation history, or extensions of Mylyn that support planning, could fail if they expected all tasks worked on to be in the Task List. Unless there is a strong use case for supporting this, and I do not recall seeing it requested, I think that we should adhere to the following design: All tasks worked on by the user (i.e., activated) are present in the Task List, unless they have been explicitly deleted by the user. If they have been deleted by the user, we should consider deleting the record of those tasks from historical traces (e.g. task activity history).
I agree with your point. It just seems to be a matter of how the task gets into the task list. My use-case is that I frequently activate tasks opened from search results and I would rather make that a one click operation than three steps: adding the task to the task list, refresh the editor, activate the task. The editor refresh is my biggest concern: It has to be closed and reopened in order to add the planning and context tab which will make the operation slow.
Per the discussion on the call, let's support this use case by automatically adding the task to the Uncategorized container. Let's add the following info message on the header along the lines of: "Task added to the Uncategorized container"
Created attachment 110197 [details] simple patch
Created attachment 110198 [details] mylyn/context/zip
Patch applied. Rob, please review the changes to TaskActivityManager.
