Due to the large number of categories we manage, our team uses Tasks to represent entire projects and Subtasks to represent the individual tasks within those projects. However, this structure creates significant issues when tracking time.
For example, if I estimate a project at 100 hours at the task (project) level, and then log time or assign time estimates to the subtasks, the system adds that time on top of the original 100 hours instead of treating it as part of the total. This results in inflated time tracking and makes it difficult to get an accurate overview of hours used on a project.
Recommendation: It would be incredibly helpful if Asana allowed users to choose whether subtask time should roll up into the parent task’s total, or be treated as part of the parent estimate—either through a setting or an optional toggle. This would provide more flexibility and prevent double-counting, especially for teams managing complex workflows.
Hi Kathleen,
Have you found a workaround for this? I have only just noticed this frustrating issue and i’m worried about changing the parent task to 0 hours in case I lose my estimated time on the subtasks?
Thanks for your help!
I could see this being useful. As long as they make it optional. I prefer to let the subtask estimates indicate what the overarching estimate would be and typically leave the parent task estimate set to 0 or set to whatever time I would spend “managing” the project itself.
Hi Skyler,
How do you prevent this from increasing your workload when scheduling work?
In your example, the 18 hours is the total estimate for the parent task/project, but it also contributes to my weekly workload. If I then add estimates to the subtasks, those hours seem to be counted on top of the parent estimate, which throws my capacity planning out and makes it look like I have more work scheduled than I actually do.
Am I understanding that correctly, and if so, how are you working around it?
Thanks!
