Community
Participate
Working Groups
There is redundancy between these two views: - the Task List needs the columns visible in Task Activity view (e.g. estimated) - when looking at Task Activity it should be possible to perform actions (e.g. activate) tasks given a timeline based perspective Fewer views is better as long as we can keep the interaction simple. We should consider merging them by giving the Task List view different display modes. This will make it possible to quickly switch between a planning and working mode, and will make the Task List modes that it can display. I.e. Show: 1) Categories & Queries: current 2) Date Ranges: day containers in Apply Mylar mode, week containers otherwise 3) Flat: no containers, useful for small lists and the Apply Mylar mode, also nice because it won't have the blank space on the left of the activate button Note that it might make sense to have a 4th "Subtasks" mode to address bug 137543, or just to make that an orthogonal "Group Subtasks" option that applies to all modes.
Isn't it sounds like "models" used by common navgator?
I've been wondering if we should explore making tasks be models post 0.6 when the 3.1 branch moves into maintenance mode, and that's related to our 'synching' of tasks as well. However, that is orthogonal to this UI discussion since the Task List's view can be flexible in the different projections that it shows of task data and can be updated if they're moved from being AbstractTaskContainer/ITask to the generic model based approach.
Mik, when are you planning to dedicate time for this issue? I've been trying to use activity view and it is quite limiting: no actions, no drag-n-drop, no quick filtering. By the way, I still think it would be convenient to allow to enable filters/working sets to the task list, so I could switch betwen tasks related to different projects where each project could have several active queries. This would also allow to see times per those project groups.
This needs to be addressed by 0.7 or shortly thereafter. As you indicate we need to fix the current limitations with the Task Activity view, and it is still marked as Experimental.
*** Bug 158406 has been marked as a duplicate of this bug. ***
Rob: why don't you prototype making date range containers be a view mode for the Task List, and let's see how we like it. There should be a container for every week, and for the current week a container for every day. This will mean that when in unfocused mode, you see all your tasks (modulo other filters, like "Filter Completed Tasks"). Then in "Focus on Workweek" mode you see tasks according to day.
Pushing to post 1.0.
I'll take this on, at least for the initial iteration.
Need to postpone to M2.
I've taken a quick pass at this. I'm able to switch between two modes now (kinda cool), but when in the 'activity' mode, as a user, the question soon arrises, "How do I add a tasks to one of the bins from this view?". With the activity view the idea was DnD but here this won't work. Right-click schedule will work but requires flipping between the two modes to do your planning (not ideal). Thoughts?
(In reply to comment #10) > I've taken a quick pass at this. I'm able to switch between two modes now > (kinda cool), but when in the 'activity' mode, as a user, the question soon > arrises, "How do I add a tasks to one of the bins from this view?". With the > activity view the idea was DnD but here this won't work. Right-click schedule > will work but requires flipping between the two modes to do your planning (not > ideal). Thoughts? -- Multiple instances of Task List view (there is an issue for that already) -- Dragging task from the task editor, i.e. from the repository icon on the header bar. -- Have "Others" bucket that could have tasks not scheduled yet
Hmm, I thought that it was simpler that that: 1) Create a new task: appears in the "Today" container with default scheduling settings 2) Drag a task to a date container: schedules it for that day, causing it to move Why would either of these not work or require switching back to the "categories & queries" mode?
(In reply to comment #12) > Why would either of these not work or require switching back to the "categories > & queries" mode? I.e. to see unscheduled tasks or tasks became outdated
If you (In reply to comment #12) > Why would either of these not work or require switching back to the "categories > & queries" mode? If a task is in a query but has yet to be scheduled it won't be available to move within the plan view. It's true that scheduling a task in the queries/cat mode will send it to the appropriate bin but I guess this will require scheduling these tasks in the q/c mode then switching to the plan mode to see the results. This is what concerns me.
Hmm. It seems like new query hits should appear in the "today" bin. But it is still unclear where unscheduled tasks would go.
Mik suggested an 'unscheduled' bin much like the archive would contain these unscheduled tasks.
(In reply to comment #16) > Mik suggested an 'unscheduled' bin much like the archive would contain these > unscheduled tasks. BTW, that archive thing is really unmanageable. You should at least make it per-repository, even for this model.
I was thinking that Archive could change into separate bins along the lines of: * Uncategorized (this would be the same as the stuff in the root category) * No matching query [bugs.eclipse.org] * No matching query [developer.atlassian.com]
(In reply to comment #18) > I was thinking that Archive could change into separate bins along the lines of: > * Uncategorized (this would be the same as the stuff in the root category) > * No matching query [bugs.eclipse.org] > * No matching query [developer.atlassian.com] Reference to "query" will be odd. Maybe you should use "Other Tasks" like in working sets...
Committed first pass. Still need to address missing 'other tasks' bin, drag and drop scheduling. Unfortunately this adds another button to the Task List toolbar. Perhaps we should consider merging the focus on workweek button and the model selection button (if can still be toggle button).
(In reply to comment #20) > Committed first pass. Still need to address missing 'other tasks' bin, drag and > drop scheduling. Unfortunately this adds another button to the Task List > toolbar. Perhaps we should consider merging the focus on workweek button and > the model selection button (if can still be toggle button). Additional button maybe not too bad, especially if we'll move history dropdown out of Task List toolbar. What bugs me more is the uppercase weekday names. Maybe you can make them regular capitalized, but use gray color for Next Week, Future, Past, etc buckets.
Created attachment 61435 [details] mylar/context/zip
Tooltips on date range containers shows elapsed and estimated times. Archive bin added to scheduled presentation so that search reveals unscheduled tasks.
Moved Task Activity into Sandbox. Added drag and drop scheduling support (can be used once bug#176669 comment#24 is fixed).
