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.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue created or updatedLinear
- LogicIs the issue's cycle the active, already-started cycle?
- LogicExclude issues from the original committed scope
- ActionFetch estimate, assignee, and change actor from LinearLinear
- OutputPost scope-creep alert to DiscordDiscord
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
- 1A Linear webhook fires when an issue is created or updated.
- 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.
- 3A second logic step filters out issues that were part of the original committed set, keeping only genuine mid-cycle additions.
- 4An action step reads the issue's estimate, assignee, and the actor who made the change from Linear.
- 5The workflow posts a formatted scope-creep alert to the chosen Discord channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
