The limitation

The Progress (Auto) custom field only rolls up completion one level deep: from a top-level parent task down to its direct subtasks. Progress from nested subtasks (level 2 and deeper) is never included in the rollup.

Impact

Any task in the middle of a multi-tier hierarchy shows a flat 0%, even when its own direct subtasks are marked complete, because from the top parent's perspective those items are nested. This makes Progress (Auto) effectively useless for deep task trees.

Confirmed not to be a config issue: the field's Subtasks completion type is enabled, and the "Complete" status is correctly categorized as Done. The 0% is purely due to the one-level rollup limitation.

Request

Allow Progress (Auto) to roll up nested subtask completion recursively across all hierarchy levels, or at minimum make the rollup depth configurable.

Current workarounds

Promote mid-tier tasks to top-level so their subtasks become direct children.

Use a Progress (Manual) field on mid-tier tasks instead.