Community
Participate
Working Groups
I have multiple queries that overlap, e.g. a query for all Mylyn JIRA tasks and a query for all tasks for a particular milestone. When I schedule a task that is matched by multiple queries it is displayed multiple times in the task list. It would be great it the task list would collapse nodes that show tasks that are already displayed by other queries.
Created attachment 85339 [details] tasklist collapsed
Created attachment 85340 [details] task list expanded
This is a long-standing challenge with the Task-Focused UI . If a view shows an element more than once, and that element is interesting, it needs to show twice. Doing automatic collapsing is not likely to be a good solution because there are common cases where there is only partial overlap between containers, unlike in the screenshot attached where there is perfect overlap. Doing selective filtering is also problematic because it breaks the contract of showing all the interesting contents within the containers that they're in. As such, the current approach is to ensure that the viewer minimizes the duplication of elements. With the Task List this is possible by setting up queries and working sets in a way that avoids duplication. For example, you could set up a working set called "Milestones" and use that for planning (I just use search). Either way we should continue brainstorming both the Task-Focused UI aspect of this and easier ways to minimize duplication in the Task List.
(In reply to comment #3) > ... As such, the current approach is to ensure that the viewer minimizes > the duplication of elements. With the Task List this is possible by setting up > queries and working sets in a way that avoids duplication. For example, you > could set up a working set called "Milestones" and use that for planning > (I just use search). Either way we should continue brainstorming both the > Task-Focused UI aspect of this and easier ways to minimize duplication > in the Task List. To the brainstorming session - alternative approach to create multiple queries is to use grouping or switch between various grouping modes and/or several Task List instances. Interestingly, new marker views, including the Problems view, now support "new view" operation allowing to clone view.
Yes, I would rather use different groupings and filters instead of creating multiple queries. Unfortunately the current support for grouping in the task list is not sufficient to cover my use cases (e.g. grouping by milestones is not supported and grouping by multiple criteria like milestone and owner is not possible either). Using searches is rather inconvenient as the search results view does not allow grouping and searches are not persisted, so I have to enter the same searches over and over. I'll try using a working set for now that only has a subset of my queries that do not overlap.
Shawn suggested that a filter or presentation could be added that uses the new data structure that tracks parents of a task to only display each task once. It would be great if we could investigate this for 3.0. Shawn would you be interested in working on this?
Note that we'll need a spec of the design before any concrete implementation.
This is too big a UI change for 3.0, let's consider for 3.1.
We still don't have a good solution to this. The problem is that we do not have a predictable way of asking the view or viewer what's already visible. We should brainstorm this further early in the 3.2 cycle.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
