* '''Support working sets.''' A Task List that includes projects from multiple "working spheres" (e.g. Project A, Project B, Personal) can become unwieldy and distracting. Integration of top-level working sets could address this.

* '''Support working sets.''' A Task List that includes projects from multiple "working spheres" (e.g. Project A, Project B, Personal) can become unwieldy and distracting. Integration of top-level working sets could address this.

* '''Support date view in Task List.''' A common way of organizing tasks to work on in the current week is by day. We should support this by integrating the Task Activity view's date range container presentation with the Task List. (147084)

* '''Support date view in Task List.''' A common way of organizing tasks to work on in the current week is by day. We should support this by integrating the Task Activity view's date range container presentation with the Task List. (147084)

−

* '''Support integration with planning tools.''' Many task repositories have facilities for task planning in the form of milestones, due dates, and other organizations of tasks. The Task List and Task Editor should support such extensions, for example, allowing the Task List to be organized by milestone. (e.g. 152490).

+

* '''Support integration with planning/calendaring tools.''' Many task repositories have facilities for task planning in the form of milestones, due dates, and other organizations of tasks. The Task List and Task Editor should support such extensions, for example, allowing the Task List to be organized by milestone. (Calendaring, privacy controls) (e.g. 152490).

* '''Support task dependencies.''' Many tasks are related to other tasks, whether it's because they should be worked on in sequence or are subtasks. We should make these dependencies explicit in the Task List and Task Editor. (137543)

* '''Support task dependencies.''' Many tasks are related to other tasks, whether it's because they should be worked on in sequence or are subtasks. We should make these dependencies explicit in the Task List and Task Editor. (137543)

* '''Improve task activity timing.''' We currently have a task activity mechanism, but it is not explicit enough, and does not capture time spent outside of the workbench. It should also be extensible to OS-specific monitoring. (135668).

* '''Improve task activity timing.''' We currently have a task activity mechanism, but it is not explicit enough, and does not capture time spent outside of the workbench. It should also be extensible to OS-specific monitoring. (135668).

−

* '''Provide workflow mechanism.''' There are many common workflows, such as commit/complete/deactivate. We should provide a mechanism for specifying and executing task-related workflows. (160780)

+

* '''Provide workflow mechanism.''' There are many common workflows, such as commit/complete/deactivate. We should provide a mechanism for specifying and executing task-related workflows. This requires direct editing of task data (i.e., without editor submission). (160780, 124224)

+

* (hyperlinking)

== Repositories ==

== Repositories ==

−

* '''Provide standard XML for for tasks.''' We should create a canonical and extensible XML for for tasks that we use for storage. Connector providers returning this form would not need custom attribute mappings.

* '''Make offline cache faster and more robust.''' The offline cache is currently one large serialized file. We should make it more robust so that changes to connectors and the framework do not cause the offline data to be cleared. This should make it possible to put a repository into offline mode permanently, and never lose the task data. (165809)

* '''Make offline cache faster and more robust.''' The offline cache is currently one large serialized file. We should make it more robust so that changes to connectors and the framework do not cause the offline data to be cleared. This should make it possible to put a repository into offline mode permanently, and never lose the task data. (165809)

* '''Improve connectivity problem and performance handling.''' Lack of or degraded connectivity should be transparent, and jobs should be cancellable. (165833)

* '''Improve connectivity problem and performance handling.''' Lack of or degraded connectivity should be transparent, and jobs should be cancellable. (165833)

* '''Improve consistency between local and repository tasks.''' Need to consider how to promote task between local and repository, and whether local tasks should be a kind of repository. (12431)

* '''Improve consistency between local and repository tasks.''' Need to consider how to promote task between local and repository, and whether local tasks should be a kind of repository. (12431)

+

* '''Provide standard XML for for tasks.''' We should create a canonical and extensible XML for for tasks that we use for storage. Connector providers returning this form would not need custom attribute mappings.

+

* (models show in task repositories view)

== Context ==

== Context ==

* '''Preserve element identity through refactoring.''' Currently only the active context participates in refactoring. We either need to maintain a dependency map to update the element handles of inactive contexts, or migrate them when they are activated, via the refactoring history. (164243)

* '''Preserve element identity through refactoring.''' Currently only the active context participates in refactoring. We either need to maintain a dependency map to update the element handles of inactive contexts, or migrate them when they are activated, via the refactoring history. (164243)

Platforms

Priorities

Committers will prioritize bugs without external contributions (i.e. patches) in the following order:

API & Tasks framework

Task List and Task editor UI

Task-Focused UI

Context framework

Connector improvements

Themes

Tasks

Increase Task Editor information density. The task editor is a very frequent target of interaction, and we need to continue streamlining it. When opened it should show the user the most relevant information with minimal clicking and scrolling required. (158921).

Support working sets. A Task List that includes projects from multiple "working spheres" (e.g. Project A, Project B, Personal) can become unwieldy and distracting. Integration of top-level working sets could address this.

Support date view in Task List. A common way of organizing tasks to work on in the current week is by day. We should support this by integrating the Task Activity view's date range container presentation with the Task List. (147084)

Support integration with planning/calendaring tools. Many task repositories have facilities for task planning in the form of milestones, due dates, and other organizations of tasks. The Task List and Task Editor should support such extensions, for example, allowing the Task List to be organized by milestone. (Calendaring, privacy controls) (e.g. 152490).

Support task dependencies. Many tasks are related to other tasks, whether it's because they should be worked on in sequence or are subtasks. We should make these dependencies explicit in the Task List and Task Editor. (137543)

Streamline task creation. Make it easier to create tasks, fork them, or promote local tasks to repository tasks. (154896, 152211)

Improve task activity timing. We currently have a task activity mechanism, but it is not explicit enough, and does not capture time spent outside of the workbench. It should also be extensible to OS-specific monitoring. (135668).

Provide workflow mechanism. There are many common workflows, such as commit/complete/deactivate. We should provide a mechanism for specifying and executing task-related workflows. This requires direct editing of task data (i.e., without editor submission). (160780, 124224)

(hyperlinking)

Repositories

Make offline cache faster and more robust. The offline cache is currently one large serialized file. We should make it more robust so that changes to connectors and the framework do not cause the offline data to be cleared. This should make it possible to put a repository into offline mode permanently, and never lose the task data. (165809)

Improve connectivity problem and performance handling. Lack of or degraded connectivity should be transparent, and jobs should be cancellable. (165833)

Improve consistency between local and repository tasks. Need to consider how to promote task between local and repository, and whether local tasks should be a kind of repository. (12431)

Provide standard XML for for tasks. We should create a canonical and extensible XML for for tasks that we use for storage. Connector providers returning this form would not need custom attribute mappings.

(models show in task repositories view)

Context

Preserve element identity through refactoring. Currently only the active context participates in refactoring. We either need to maintain a dependency map to update the element handles of inactive contexts, or migrate them when they are activated, via the refactoring history. (164243)

Infrastructure

Generalize task and context storage mechanisms.'

TO FILE

Europa-related

163537: Use Eclipse Activities (Capabilities) to switch Mylar on/off

167362: move httpclient dependency to Orbit

build process

167050: Optimize Mylar update sites

166733: Mylar update site should link to companion update sites

UI Finessing

143577: alt-click to expose filtered queries/categories in tasklist

163450: Tab title decoration for Task List view

166990: [multi monitor] if Eclipse is on secondary monitor to left of primary task list tooltips show on primary

166644: Activating task should restore multiple editor configuration

150682: Context attachment needs progress indication with cancellation or to run in background

159318: [ui] retrieve context action is not available in the attachments popup menu

166621: Include a "Add Attachment" action on task context menu

158405: Add sort indicators to the Task List table view

Misc:

166399: allow contributions to the UI legend

162610: automatically toggle folding of Javadoc comments

161877: make searching for duplicates more encouraged and more flexible