TICKET MANAGEMENT

Flag mid-cycle issues added to an active Linear cycle and post a Discord scope alert

Watches for issues attached to the current Linear cycle after it started, and posts a real-time Discord alert naming the issue, its points, and who added it.

CategoryTicket Management
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLinear issue created or updatedLinearLinear
  • LogicIs the issue's cycle the active, already-started cycle?
  • LogicExclude issues from the original committed scope
  • ActionFetch estimate, assignee, and change actor from LinearLinearLinear
  • OutputPost scope-creep alert to DiscordDiscordDiscord

What it does

When an issue is assigned to a Linear cycle that is already in progress, this workflow detects that the cycle's planned scope has changed and posts an immediate alert to a Discord channel. The alert names the issue, its estimate, the assignee, and the person who added it, so the change is visible the moment it happens rather than at cycle end.

When to use it

Run this when your team commits to a cycle scope at planning and you want a lightweight guard against silent additions. It is ideal for squads that protect focus time and want every mid-cycle insertion to be a conscious, discussed decision.

How it works

  1. 1A Linear webhook fires when an issue is created or updated.
  2. 2A logic step checks whether the issue's cycle is the team's currently active cycle and whether the cycle's start date has already passed.
  3. 3A second logic step filters out issues that were part of the original committed set, keeping only genuine mid-cycle additions.
  4. 4An action step reads the issue's estimate, assignee, and the actor who made the change from Linear.
  5. 5The workflow posts a formatted scope-creep alert to the chosen Discord channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  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.