Hi,
In Bryntum Gantt, if we have a dependency chain like T1 → T2 → T3, and task T2 is cancelled (inactive), then T3 gets aligned to its parent’s start date.
In Microsoft Project (MPP), the same scenario behaves differently: when T2 is cancelled, T3 is scheduled after the end date of T1, effectively honoring the indirect dependency T1 → T3.
How can we configure Bryntum Gantt to replicate MPP’s behavior, so that downstream tasks continue to respect the logical predecessor chain (e.g., T1 → T3) even if an intermediate task is cancelled(inactive)?
Please find attached screenshots for reference.
Thanks & Regards,
Sagar Shivgan