Gantt Charts

Link Mode

How Link Mode shifts dependent items when a due date moves, what triggers the cascade, where the Gantt toggle overrides the organization default, and what happens when it is off.

Link Mode keeps a dependency chain consistent when a date slips. With it on, moving an item's due date moves every item that depends on it by the same number of days, and the shift carries on down the chain. With it off, you move one bar and decide the rest yourself.

There are two switches. The organization-wide Enable Link Mode setting (on by default) governs date changes made anywhere in DevStride and through the API. The Linked / Unlinked toggle on a Gantt chart overrides it for changes made on that chart.

What the cascade does

Say the API epic is due 10 June and the mobile epic, which depends on it, runs 11 to 25 June. You drag the API epic's due date to 17 June, a 7-day slip.

  1. DevStride measures the change: new due date minus old due date, 7 days.
  2. Every item that depends on the API epic has both its start and due date shifted by 7 days: mobile now runs 18 June to 2 July.
  3. Each of those items passes the same shift to whatever depends on it, and so on through the whole chain.

Details that matter:

  • Only a due-date change starts a cascade. Moving a bar changes both dates and so cascades; resizing only the start edge does not.
  • The shift is the same number of calendar days for everything downstream. Weekends are not skipped, and gaps you set between items are preserved. Link Mode does not pull a dependent forward to butt against its blocker.
  • Only Dependency links propagate. Items joined by a Related link are never moved.
  • Workstreams, items and milestones all take part. Workstreams and items have both dates shifted; milestones have their single date shifted.
  • Adding a dependency also schedules. In Linked mode, if you link item B as dependent on item A and B currently starts on or before A's due date, B is moved to start the day after A ends, keeping its duration.
  • Big chains take a moment. The Gantt shows Saving dates... until the cascade has finished; the number of affected items decides how long.

Where each switch applies

You change a due date inCascade is decided by
A Gantt chart (drag, resize, table cell, Shift + click)The chart's Linked / Unlinked toggle. The organization setting is ignored here.
The item workspace, Items Table, Map or a boardThe organization's Enable Link Mode setting
The API or the DevStride MCP serverThe request's own staticMode value if provided, otherwise the organization setting

So with the organization setting on, a due date edited in the Items Table cascades just like a Gantt drag in Linked mode. With it off, only Gantt charts in Linked mode cascade.

The Gantt toggle

The link / unlink button in the chart's control strip switches modes; Shift + M does the same.

  • Linked mode (link icon): Item actions will propagate down the dependency chain.
  • Unlinked mode (unlink icon): Item actions will not propagate to its dependency chain.

Your choice is remembered in your browser across charts and is stored in saved views, so a view can open a chart in the mode its audience expects. Scenario recordings note which mode each move used. See Navigating the timeline.

Outside the Gantt, with the organization setting off, DevStride does not move dependents but it does check. If a new start or due date conflicts with a related item's dates, a Relationships Date Warning dialog explains the conflict and asks you to Confirm or Cancel. Turning the setting on replaces the warning with the automatic shift.

On a Gantt in Unlinked mode, the bar you move is the only one that moves. Dependency lines stay drawn, so an overlap shows up as a line pointing backwards.

Setting the organization default

Admins change the default in Configure Settings → Admin → Global Automations: tick or untick Enable Link Mode (Allow item actions to propagate down the dependency chain). It saves immediately. The same page holds Sync work item dates with their cycles and Automate New/Done, which are separate settings. See Global Automations.

Set up a chain that keeps itself in sync

  1. Record the dependency: on the Gantt, drag from the blocker's connector to the dependent and choose Dependency, or in the item's Relationships dialog add the blocker under Dependencies. See Manage and Edit Dependencies.
  2. Position the dependent once, with whatever gap you want after the blocker.
  3. Make sure Link Mode is in effect for where you will edit: the chart toggle on the Gantt, or the organization setting elsewhere.
  4. From then on, when the blocker's due date moves, the dependent and everything behind it move with it.

Before a large move, open the Dependency Graph to see how far the cascade will reach, or rehearse it in a scenario.