Hans Heijmans
Description:
The "Remap Parent Task Dates based on Subtasks" feature currently only updates the top-level ancestor tasks when a subtask's date changes. It skips intermediate parent tasks in a nested hierarchy.
Example:
Task A (parent)
Task B (subtask of A)
Task C (subtask of B)
When I change Task C's due date, Task A's due date updates correctly, but Task B (the direct parent of C) does not update. This makes the feature unusable for anyone managing projects with more than one level of subtasks.
Expected behavior:
When a subtask's date changes, every parent in the chain should update its start/due dates accordingly:
  • Task B should update to reflect Task C's new dates
  • Task A should update to reflect Task B's new dates
  • This should cascade through all levels, regardless of nesting depth
Why this matters:
Many project structures require intermediate grouping (e.g. Epics → Features → Tasks, or Project Phases → Work Packages → Activities). Without recursive date rollup, users are forced to either flatten their hierarchy (losing organizational clarity) or manually update intermediate tasks every time a date shifts.
Other project management tools (MS Project, Smartsheet, Primavera) handle this recursively by default. ClickUp's nested subtask support (up to 7 levels) suggests deep hierarchies are a supported use case, but the date rollup doesn't match.
Request:
Make "Remap Parent Task Dates based on Subtasks" cascade through all parent levels in the task hierarchy, not just the top-level ancestor.