Sub-tasks

  • 98Views
  • Last Post 19 February 2018
  • Topic Is Solved
0
votes
haug posted this 09 February 2018

I noticed that when I track time against a sub-task in Asana, tmetric does not recognise the hierarchical relationship between the two and consequently does not add the time spent on the sub-task to the time spent on the task. This is unfortunate and makes tmetric unusable for me.

But maybe I missed something?

Order By: Standard | Newest | Votes
0
votes
Aleksandr Serdyuk posted this 09 February 2018

Indeed, each sub-task is tracked separately. We'll revisit the integration and think on improvements.

As a workaround, you can start timer on a parent task copy the sub-task's description to the time entry description. TMetric will keep the link to the parent task and in the detailed report you'll be able to see all sub-tasks.

0
votes
haug posted this 09 February 2018

 We'll revisit the integration and think on improvements.

That's good to hear. Beware, the Asana task hierachy is sophisticated (it not only has sub-tasks and sub-sub-tasks) but you can also insert sections (by adding a colon to the end of the task name) so that my guess is that you will not be able to properly identify a task's position in the hierarchy without going through Asana's api, right?

copy the sub-task's description to the time entry description

What do you mean by that? I don't see any "time entry description" in tmetric except for the field where the task name appears. 

Besides, that work around is not feasible in practice as it means that you have to navigate from asana to tmetric every time you start a sub-task in order to modify the entry there. 

Also, even if this would work at the level of task and sub-task, what about sections in Asana. Sometimes a task is directly under a project, and sometimes it is under a section which is under a project...

To be honest, I think yopu should stop advertising that tmetric integrates with Asana. It's not true.

 

0
votes
Aleksandr Serdyuk posted this 09 February 2018

What do you mean by that? I don't see any "time entry description" in tmetric except for the field where the task name appears. 

That's correct. Edit task name and past a subtask name instead.

0
votes
haug posted this 09 February 2018

So do I read you correctly: you don't have any intentions in fixing this any time soon, right?

0
votes
Aleksandr Serdyuk posted this 12 February 2018

I didn't say that. But I'm not sure that it's even technically possible for us. As I said above we'll investigate this.

We some 40+ integrations and they all share the same approach to connecting with third-party tools.

 

0
votes
haug posted this 12 February 2018

Okay, thanks for investigating. 

 

I understand that Tmetric's approach to integrations is to basically scrape the other services web-page via the browser plugin. That's why I mentioned above that you would probably need to use the Asana api to make sure that the task ID that you get via the browser plugin is interpreted correctly, i.e. that its time is tracked against the correct parent task (and to reflect changes if the task is renamed or moved in Asana).

But the biggest limitation is probably that Tmetric itself is extremely flat, i.e. it only supports two levels in the task hierarchy - projects and tasks. My hunch is that the only way to properly integrate with Asana (and other services with a deeper task hierarchy) is to introduce sub-tasks, sub-sub-tasks (and so on) in Tmetric itself.

0
votes
Artem Avramenko posted this 19 February 2018

We will support subtasks in the next version of the extension. Subtasks and sub-subtasks will be shown as custom description of root task, so all of them will be linked to same task.

It is suitable to your needs?

0
votes
haug posted this 19 February 2018

We will support subtasks in the next version of the extension.

That is good news!

Subtasks and sub-subtasks .

What about sub-sub-subtasks? (and so on)

will be shown as custom description of root task, so all of them will be linked to same task

Well, I'm not sure whether "linked" is the right term. Aren't they are simply merged into the root task? What does this mean for reports? Will reports be brokern down into sub-tasks? What happens when a sub-task is renamed? Are you sure you will be able to rename that custom description appropriately? 

To be honest, I think putting sub-tasks into the custom description is the worst of all paths to go down. You're basically hacking your own ill-designed data-structure to create a work-around. Even if you have good answers to the questions above, it will cause all kinds of problems when people start editing the custom description in Tmetric etc. Maybe there is a workable hack with tags, but even that will still be a hack. If you really want to support task-hiearchies, you'll need to implement it properly, i.e. add it to the native Tmetric data structure. Take a look at Timecamp. They've done it right.

0
votes
Artem Avramenko posted this 19 February 2018

What about sub-sub-subtasks? (and so on)

They will be supported too.

Will reports be brokern down into sub-tasks?

Tasks Summary will show a single row with rooot task. Detailed Report will show all subtasks without hierarchy.

Are you sure you will be able to rename that custom description appropriately?

You can rename them, and logged entries will be still linked with root task, but with old descriptions.

 If you really want to support task-hiearchies

We have no such plans at the moment, so we propose the solution that can be implemented in the nearest future.

0
votes
haug posted this 19 February 2018

I appreciate that you are trying to find a solution that can be implemented soon, but, as I said, I think it is a bad bath to go down. I just realize another huge problem with how you're planning to do it:

Tasks Summary will show a single row with rooot task. Detailed Report will show all subtasks without hierarchy.

That means you solved the problem that sub-tasks become separate tasks in Tmetric, but only for the first level of sub-tasks. At the next level, another variant of the same problem comes up again: if I understand it correctly, sub-sub-tasks will *only* be counted against the root task, not against the sub-task, i.e. their immediate parent task, right? That is the same as the current situation except that the problem has move one level down the hierarchy...

 

Close