When using the list view, I have subtasks at the same level as the tasks. How can this be changed to show only subtasks under their parent task?
1 Like
You probably have “Complete Screening”, which is meant to be just a Subtask, added explicitly to the Project in question. That will cause this appearance. The solution would be to remove “Complete Screening” from the Project.
I can see that the sub-task Complete Screening was added from a rule, so it was not added manually.
I tried to remove the complete screening by deleting it, but it removed it from task 11 as a sub-task.
Are there other reasons why sub-tasks would appear in the parent task section?
Then it’s set to be assigned to the project from within the rule.
To remove that particular subtask, open its detail pane and remove it form the project there.
To keep this from happening in the future, edit the rule, go to the subtask within the rule action, and remove it from the project there.
1 Like
I am looking for a way to keep the subtask from being removed from the project. I want to prevent it from appearing twice within the parent task and in the list view for the parent tasks. It appears that this sub-task is a parent task.
No other sub-tasks appear in the list view of parent tasks.
So, based on the screenshot, I have added task 8 as a sub-task that appears under task 11. Why would it appear again?
That’s just the way Asana works: subtasks by default are not attached to the project of their parent task (or to any project); when you do attach a subtask to a project, Asana displays it in the list view at the top level as if it’s a top-level task, in addition to displaying it as a subtask - as you’re seeing. There’s nothing you can do about that behavior; the only way to prevent it is to remove the subtask’s attachment to the project.
Another thing some people do is to create a section in the project called something like “Subtasks - please ignore”, make that the bottom section in the project, move all of the “extra top-level” subtasks to that section, and keep the section collapsed. Out of sight, out of mind.
But another question is: why do you feel the need to have the subtask attached to the project? There are a few good reasons to do so, but not too many. Most subtasks live happily without actually being attached to the project.
3 Likes
What happened with me was, I had a task in the list view. Then I converted it into a subtask of another task.
In list view it now appears twice, once under its section, and again, nested as a subtask under its task.
You can replicate this very quickly.
Create a task called “I am a task”
Then create another task called “I was a task, but was converted into a subtask”
Then convert the second task into a subtask of the first.
If you’re looking at the list view, you’ll see the subtask appear as a nested task, and also remain as a task under the section.
This is because as Phil points out, the subtask is still associated with the project.
To remove it from the list view, and leave it nested, you have to remove the project from the subtask. Counterintuitive.