PROJECT MANAGEMENT

Cascade Linear due dates when a blocking issue is delayed

Detects when a Linear issue's target date is pushed out and walks its blocks-relationship graph to extend the target dates of every transitively blocked issue.

CategoryProject Management
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLinear issue target date updatedLinearLinear
  • LogicConfirm date slipped later; measure gap
  • ActionWalk blocks graph for downstream issuesLinearLinear
  • ActionExtend each blocked issue's target dateLinearLinear
  • OutputDM affected assignees in SlackSlack

What it does

This workflow treats Linear's "blocks" relationships as a dependency graph. When a blocking issue's target date moves later, it traverses the chain of issues that depend on it and extends each of their target dates so the schedule stays consistent end to end.

When to use it

Use it when your team relies on Linear's blocks/blocked-by links to model sequencing and a single late issue should ripple through everything downstream of it without a manual audit.

How it works

  1. 1A Linear webhook fires on an issue update where the target date changed.
  2. 2A logic step confirms the new date is later and measures the gap.
  3. 3The workflow recursively gathers all issues reachable through outgoing "blocks" relations.
  4. 4For each blocked issue it pushes the target date forward by the gap, capping at any hard deadline label.
  5. 5It DMs each affected assignee in Slack with the old date, new date, and the originating issue.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.