LoginSign Up
← Back to all sparks
Asana logo

Asana

PMCOLLAB
Velocity5.0

Work management platform for teams

asana.com ↗

Asana keeps fixing subtask plumbing: types now follow the parent, dates roll up.

work-managementgovernanceplanningautomationenterprise-admintask-hierarchy
◆Current state
Asana's fall releases split between control-plane work and planning mechanics. Subtask types are now set by the parent task rather than the project view they're added from, with a per-custom-type choice to inherit or default to basic Tasks. That follows Subtask Date Rollups, automation rules running on their owner's current permissions, a reorganized Admin Console with AI as its own section, and threaded comments.
◆Where it's heading
The summer sparks (AI Teammates, agent-built rules, Slack @mention capture) widened what Asana can do; the fall has been about making that safe to deploy and keeping task structure consistent. Predictable subtask types and dates matter because automations and AI Teammates read that structure, so cleaner hierarchies make both more reliable.
◆Prediction
Expect more hierarchy consistency work, such as rollups that run automatically or via rules, and admin controls for AI Teammates in the new Admin Console AI section.

◆Recent moves

  1. 14d ago

    :puzzle_piece: Subtask types now follow their parent, across projects

    A second subtask fix in a week: the parent task now decides a subtask's type, so the same parent behaves the same in every project it lives in. Custom task types get an inherit-or-basic toggle, which keeps request-style workflows (a Laptop Request with plain fulfillment tasks) clean. It continues the fall pattern of tightening the structure that automations and AI Teammates depend on.

    View source ↗
  2. 20d ago

    🗓️ Subtask Date Rollups: bring your parent dates up to date

    Subtask Date Rollups set a parent task's start and due dates from its earliest and latest subtask dates, through nested levels and across many parents in one action. It is a planning-accuracy fix that sits under the AI features, which answer status questions from exactly these dates.

    View source ↗
  3. 23d ago

    A clearer way to find your Admin settings 🧭

    The Admin Console reorganization gives Asana AI its own settings section and groups Work, Timesheets and Budgets under a Product area. It is navigation, not new controls, but it shows Asana now treats AI and add-ons as separate things admins govern.

    View source ↗
  4. 29d ago

    🔐 Automation rules now use their owner’s current permissions

    Rules now execute with their owner's current permissions instead of the access they had at creation. That closes a quiet privilege-retention gap, which matters more as AI Teammates start authoring rules on users' behalf.

    View source ↗
  5. 1mo ago

    🗂️ Bulk-add from Portfolio now works for editors and admins!

    Portfolio bulk-add now covers every project a user can share, not just those they administer. It is a small permission-model cleanup consistent with Asana's move from team-bound ownership toward role-based access.

    View source ↗
  6. 1mo ago

    No more stringing you along, Threaded Comments are now LIVE 🧵

    Threaded replies arrive on tasks, goals, messages and status updates across web and mobile. It is a parity feature Slack-native teams expected, and it keeps side discussions inside Asana rather than spilling into chat.

    View source ↗