A parent task can say Friday while one of its subtasks runs into the following week. Asana’s Subtask Date Rollups, announced on October 8, addresses that mismatch by calculating parent dates from the work underneath them.
When someone runs a rollup, the parent’s existing start date follows the earliest subtask start, and its existing due date follows the latest subtask deadline. Nested and completed subtasks count; undated ones are skipped. Asana’s announcement stresses two limits: rollups are manual, and they do not create missing parent dates. A date warning alone changes nothing.
A cleaner schedule still needs a decision
Consider an onboarding task covering account setup, training, and an access review. Rolling up its dates before a planning meeting could expose that the parent no longer represents the actual work. If training slips again, someone must run the rollup again.
Watch the margin around that plan. A parent may deliberately include time for review or unexpected delays; matching the subtasks can remove that buffer. Asana also warns that project-wide rollups cannot be undone. Inspect a single representative task first, then decide which dates should describe the detailed schedule and which represent a commitment to the rest of the team.
