Indicator for Sub-Tasks

[lpb]

Hi @Tyler_Spencer, Perhaps these posts, and others in each thread, might help:

See whether a task has subtasks without drilling down

@Mark_Spencer, Did you notice the faint right arrow at the far right of the task’s entry in the tasks list? It’s not perfect, but if a task has at least one subtask, a description, or attachment, it will appear. If it has none of those, it will not show. So it’s an imperfect indicator for you (but maybe better than nothing!) in that you can only be confident there are no subtasks if also there is no description or attachment. Additionally, I discovered there’s a bug in Asana if you remove the l…

What does the carrot at the end of a task mean

Fwiw, often I manually designate tasks that have key task details (e.g., subtasks) that I don’t want to miss, especially when many tasks in the same project don’t have task details. I just add my own " >" at the end of the task title. It’s a pain but it’s been a long time and doesn’t see Asana wants to alter how they indicate task detail info.

Survey of Users Creating Subtasks to Subtasks

Hi @James_Carl, I generally avoid subtasks of subtasks, and recommend the same to others except in special circumstances.

In general, a lot of folks have been burned by trying to accomplish too much with subtasks, but I swear by them for what they’re good at: breaking down a task and/or adding structure to a task’s content, but not expecting a whole lot more than that out of them, generally.

Hope that helps,

Larry