My team works on tasks and subtasks, and everything they work on is on my sprint board. I’m trying to pull analyses on their accomplishments this year and want to see all tasks or subtasks that are associated with the project on the dashboard. I don’t want to see any subtasks that are not in my project.
When I choose “Don’t show subtasks” on the Subtask filter, it excludes subtasks not on the project (GOOD) but it also excludes any subtasks that are on the project (BAD).
If I choose “Only show subtasks,” it includes subtasks not on the project (BAD) and excludes tasks on the project (BAD).
If I don’t use that filter whatsoever, it includes tasks and subtasks on the project (GOOD) but also includes subtasks not on the project (BAD).
I tried filtering to only include assignees on my team, but I’m unable to include counts for anyone who has left the team and to exclude everyone else is not sustainable.
For now, I’m leaving the filter blank but would be great to have a way to report on everything in the project, no matter if it is a task or a subtask, and exclude things that are not in the project.
Do you mean a subtask of a task in the current project that is also multi-homed into another project? I don’t understand how a subtask that is counted shouldn’t in your case…
I’m going off the principle that “subtasks don’t inherit the project.” If this is still the case, then the subtask is technically not part of the project, and therefore, in this particular instance, I don’t want that to be counted in my reports.
I originally thought that the “don’t show subtasks” filter meant “exclude subtasks of tasks in the project” but that doesn’t seem to be the case.
Eg. in a multi-tiered task hierarchy (A > B > C) where B is in the project, this task won’t show up using this filter bc B itself is a subtask of A.
Essentially, I’m looking for a way to report on only the tasks on the project, irrespective of where in the task hierarchy it sits.
We have run into trouble with the dashboard and reporting filter to include or exclude subtasks strictly by general task type.
Our use case is an overarching project where items from multiple different projects get sent through process stages, picture KANBAN columns. Some of the items are subtasks (as in user stories) of bigger epics in their respective “home” projects — but get assigned as main tasks to the process board in question. Because here they are the decisive packages of work in progress.
Now, “exclude subtasks” will hide them from the item count on the project dashboard.
“Include subtasks” won’t work consistently either, because as it happens, some tasks on the board carry subtasks of their own. Not as work items on that third level, but as checklists with conditions of satisfactions for testers to check off.
Is there a way for me to go filtering “exclude tasks which are subtasks here on this project”?
+1 the way the Subtasks filter works when trying to create a chart that Includes tasks from a Specific project is terrible.
I want to create a chart that shows only tasks which have been added to a specific project.
I don’t want this chart to show any subtask UNLESS the subtask has been specifically added to the project so everyone that visits the project see’s that subtask directly alongside all of the other tasks that are in the project.
I do want this chart to show every task that has beed added to this specific project, even if it just so happens that one of these tasks is itself a subtasks of a parent task that doesn’t live in this project.
Please flag this absurd chart filtering behavior to the top of the product team’s bug fixes.
Same here. We have a Sprint board where tasks from other projects are added. These tasks can be either normal tasks or subtasks (of epics for example). I want to be able to build a chart for the Sprint board that takes into account only the tasks on the Sprint board, regardless of if they have subtasks themselves, are normal tasks, or are subtasks or others. Currently there is no way to achieve this.
I am also struggling with this. My current workaround is adding an additional filter for a custom field that is used consistently on the parent task (which is a subtask from another project) that will most likely won’t be used on the subtasks. So far that has been working but there is room for error here.