Bug Report: Critical Path fails to surface “starts-too-early” conflicts (upstream chain not highlighted; successor sometimes not highlighted)
Summary
When a successor is scheduled to start before its predecessor chain can finish, Critical Path often does not surface the blocking path. In some cases it highlights only a faint dependency line (barely visible), and not even the successor task itself. Only when the successor is scheduled to start immediately after the predecessor finishes does the whole chain highlight correctly.
Expected
-
The full blocking chain and the successor S are highlighted as critical, clearly signaling an infeasible start for S.
Impact
-
Reviewers can miss real schedule conflicts; predecessor chains are not re-planned to finish earlier; downstream slippage occurs.
Request
-
When S starts before predecessors can finish, automatically highlight the entire upstream critical chain and the successor.
-
Ensure a consistent, visible treatment (task highlight, not just a faint link) so conflicts are unmistakable even when groups are collapsed or the view is busy.
Examples
Hello Teemu Nurminen, thank you for sharing such a detailed post! We will make sure to share it with the relevant team 👍
Rohan V Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover
Rohan V Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover