Community
Participate
Working Groups
Quoting Steffen: The naming of "Group Subtasks" is not very clear. "Filter Subtasks from Query" would be more accurate: If a tasks is matched by the query and also a subtask of a matched task it will not show under the query node when the option is enabled. I wonder if this option should be always on (to remove duplicated entries from the task list) and new option should be provided that would allow to flatten the task list. The latter is often more convenient when dealing with scheduled tasks or when planning.
+1 I would like to have a mode in the task list that is something like "Show results matched by query only". I would like to configure this on a query or working set basis for my planning queries. How about making this a configuration option in the sandbox that is contributed to the task list popup menu or task list view menu?
Sure, we could try it in the Sandbox and see if there is something simple that could be generalized.
May I suggest to keep it simple and just provide a global option "show sub-tasks". By the way, what is the value of not grouping subtasks anyways? It seem like its name is confusing and it is unlikely that random Mylyn user knows what it actually does.
I don't see much value in not grouping subtasks. I think the main driver we had for it was the fact that not all Bugzilla users make use of blocks/depends-on for nesting subtasks (e.g. many Eclipse projects don't, while more Mozilla projects seem to). The problem with "Show Subtasks" was that some repositories require subtasks to be shown (e.g., Rally) so they could not adhere to such an option.
(In reply to comment #4) > I don't see much value in not grouping subtasks. I think the main driver we > had for it was the fact that not all Bugzilla users make use of > blocks/depends-on for nesting subtasks (e.g. many Eclipse projects don't, while > more Mozilla projects seem to). It doesn't seem like Mylyn currently addresses those users needs, because subtasks are always shown and can't be turned off > The problem with "Show Subtasks" was that some repositories require subtasks > to be shown (e.g., Rally) so they could not adhere to such an option. Not sure if "require to be show" is correct statement. Some repositories are indeed hierarchical by the nature, but it doesn't mean that tasks from those repositories can't be flattened out.
*** Bug 213858 has been marked as a duplicate of this bug. ***
I think we have to fix up this confusion for 3.1. In addition, fixing this will mean that people can set up queries in a way where subtasks don't cause an aribratry number of additional tasks to match the query.
Since this bug originally requested enhancements of the presentation of subtasks which is out of scope for 3.2 I have made bug 208089 the current plan item. Bug 239378 links the relevant tasks for discussion of future presentation improvements .
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
