Multiple dependencies between the same 2 tasks

English Forum Product Feedback
1

Currently we can define only 1 dependency between 2 tasks. Why?

I want a task to happen in the middle of another one, Hence I need SS and FF dependencies between the same 2 tasks.

Typically the first task will have long duration, and the second one will be planned based on dependencies with other tasks (but still within the first task!).

2

Sounds like something that indeed cannot be done with Asana. It also sounds like a very specific use case in project management that might be the reason why this is not covered. The “why” is simply that it is not useful to 99% of users, might be the reason why you didn’t make the cut.

3

Well it will be the case for all support tasks: any support task shall happen within the supported task. So it does not look very specific to me, especially if you have a lot of resources to manage.

I am also missing some other stuff regarding the API, which are not planned to be implemented. So I guess I belong to the 1% users who may leave Asana.

4

Could you elaborate to the why behind the needing for these dependencies?

This is helpful in suggesting workarounds.

Also, don’t forget to vote for your own feedback. :wink:

5

@Erik_Labadie, If you’re open to a workaround until/if Asana offers the feature you request, did you already rule out the use of subtasks as a way to accomplish what you’re seeking right now?

Thanks,

Larry

6

sub-tasks are not the way I want to go because:

  1. It is anyway possible to define a sub-task outside the time window of its parent
  2. Parent and child tasks are then grouped in a way that is not my primary focus (see example below)
  3. In my own internal analysis & planning tools I dont want to distinguish between task and sub-task, I just want to consider the dependencies between tasks (therefore I need to be able to define them…)

Here is an example.

I have lots of tasks for my SW team, which are driven by the lifecycle of the SW. But I want SW team to also support the system requirement team by reviewing parts of the system requirements. The requirement tasks are driven by the lifecycle of the system activities. I dont want to first mix SW and system tasks (this would also make resource management even more difficult), I just need some dependencies between system and SW…

1 Like