When a task has multiple "blocked by" dependencies, and I change the due date of one of the blockers, the dependent task's start date is shifted by the same number of days as that single change. However, this can move the dependent task's start date to before the due date of the other blocker, which breaks the logical constraint that the task should only begin after all of its blockers are complete.

Expected behavior: When rescheduling dependencies, ClickUp should evaluate all incoming "blocked by" relationships and set the dependent task's start date to the day after the latest blocker's due date (respecting non-working days if that ClickApp is active). This is standard critical-path logic in project management tools.

Current behavior: The dependent task is shifted by a flat delta based only on the blocker that was edited, ignoring other active blockers entirely.

Use case: In construction and real estate development, we routinely have tasks that depend on multiple parallel workstreams finishing before the next phase can begin. The current behavior forces us to manually fix dates every time one blocker is adjusted, which defeats the purpose of automatic rescheduling.

Thank you for considering this improvement.