Hello Asana Community,
I wanted to raise a general observation regarding task dependency relationships and automation in Asana.
While Asana supports dependencies between tasks, the specific dependency relationship types-such as Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF)—are not exposed via the public Asana API.
As a result:
-
When building automations using Script Actions, the Asana API, or external platforms,
-
It’s not possible to determine the exact relationship type between two dependent tasks,
-
Which makes it difficult (or impossible) to accurately automate date shifting or schedule recalculation in a way that mirrors native UI behavior or traditional project-management tools.
This limitation affects general automation scenarios, especially for teams attempting to:
-
Automate duration-based scheduling
-
Programmatically maintain dependencies
The dependency data returned by the API allows identifying which tasks are related, but not how they are related (i.e., the dependency type), which restricts automation logic to assumptions rather than explicit rules.