I’m looking into Dependency shifts using the various dependency types to assist in keeping times buffered. Currently if I have a task (Task C) that is dependent on multiple other tasks completion (Tasks A and B), if I shift just the dates for Task A, then Task B doesn’t shift but C will. If I then say, yes I want B to shift as well, C adjusts again. Changing the Dependency Type doesn’t seem to do anything about it.
In order for A and B to shift, with C also shifting with buffer, do I need to have dependencies between A and B as well? Even if they’re not really related?
Example: Kickoff Meeting Task A, S&E Meeting Task B - Meetings Completed Task C (spurs dependency for next step). Shifting the Kickoff Meeting will shift Meetings Completed but not S&E (great!), but then shifting S&E will shift Meetings Completed again when I update that one.
Hi Beth! Thanks for writing in. We don’t currently support buffering (but hope to in the near future). I don’t think this issue looks like a buffering problem at a glance though!
If I’m understanding your problem correctly you have a dependency chain set up something like
A —> C
B —> C
With no relationship between A and B. In this case, if you have your dependency settings set to maintain on all buffer (the default is downstream only) then you should see B move.
1 Like
The problem then is that we wouldn’t necessarily move B. It’s a separate meeting. But if it does shift, then all downstream tasks move again when they may not need to. Lots of clicking into the Dependency Shift settings, when Asana offers Dependency Types that don’t currently seem to do anything.
Any thoughts here on what those Dependency Types COULD/SHOULD do, best case scenario?
i.e. if the F-F setting could potentially mean consume buffer, while F-S could keep the buffer?
I understand this functionality is not there now, but if I can use the dependency type setting to assist teams to know how to change dependency settings when they need to shift dates, that may be useful. And maybe Asana functionality will catch up.
Could you clarify with screenshots of the timeline to compare the current behaviour with the behaviour you’d want?
I’m having a hard time wrapping my head around it. 
@Beth_Seeber With the way dependencies are set, using Asana terminology, if a Blocking task is moved, it will move the Blocked By task. This is as designed. Asana does not take into account multiple task dependencies. It only knows that the Blocking task is being moved, therefore, the Blocked By task also needs to move.
From the previous posts, I think this is understood.
What can change is the type of dependency (Finish to Start is the default). This is done at the task level.
You can also set Dependencies to maintain buffer, consume buffer or none. None means that if a Blocking task is moved the Blocked by task will not. This is set at the project level. Click the down arrow next to the project name and select Manage dependencies.
@Beth_Seeber FYI the Dynamic Duration and Auto-Adjust workflows in our Flowsana integration do take into account multiple dependencies and both work the way you want; that is, in your example if you shift Task B but in doing so, it’s still due prior to Task A, then Task C will not shift.