Hello, we are using Asana from long time and integrate Everhour at the beginning to track properly our work, recently, based on a deep check of our time report we discover that actually Everhour doesn’t track time under an unspecified level of subtask, so in our report we missed an huge amount of hours as the function “aggregate subtasks time to parent task” doesn’t works. We notify this issue to Everhour that reply us “yes, there is this issue… Asana ask us to stop track everything because it create a pressure to the Asana API”, so my question is, any of you knows about that or there is informations about the level fo subtask are actually tracked by Everhour? Thanks
Hi @Ivan1 , welcome to the forum 
I would expect that the good folks at Everhour would be able to tell you how many levels deep of subtasks they support, no?
I would also consider, if possible, to not go more than one level deep with subtasks, as a rule of thumb, irrelevant to how many levels deep that Everhour may support.
Often it’s pretty safe to go two levels deep with subtasks, I feel, because you can expand a project’s main tasks lists to show the first level of subtasks, then click them to navigate among them, exposing the second level in the right task detail pane. Just don’t use more than you can see there: title, completion, assignee, due date (not second level subtask description, for example).
Thanks @Richard_Sather , I had a conversation about that with Everhour support team, first reply by their side was that Everhour can track maximun 2nd level, but after some inspecting test from both side we found that actually it can track more under, we test until the 5th level and it works. So based on this test we carry on with our actual tracking structure but at today we don’t have an official reply who confirm which level of subtask you can track.
Another important feedback by Everhour is related the report configuration to properly show the subtask tracking, you must use the “Parent Task” element in report instead of “Task”, in that way you can see the details of every subtask tracking.
About the level deep, We know about the the best practices of task and subtask, but we use the shifted approach of project ( in our account project=client task=project subtask=task ) in this way we can have a better organized structure based on our business where we manage many micro-projects for some clients, so it happen we need sometimes to manage a subtask deep lower than 2nd layer
1 Like