TICKET MANAGEMENT
Escalate Linear cycle scope-budget breaches to Microsoft Teams and PagerDuty
Tracks cumulative points added to the active cycle and, once additions cross a set threshold, escalates with a Microsoft Teams message and a PagerDuty alert to the cycle owner.
How it runs
The automated pipeline, trigger to output.
- TriggerIssue joins active cycle (Linear webhook)Linear
- ActionRecompute cumulative points added since startLinear
- LogicHas cumulative addition crossed the scope budget?
- ActionPost breach detail to Microsoft TeamsMicrosoft Teams
- OutputOpen PagerDuty alert to cycle ownerPagerDuty
What it does
This workflow maintains a running total of points added to the active Linear cycle after planning. While additions stay under your scope budget it stays silent. The moment cumulative additions cross the threshold, it treats the breach as an operational event: it posts a detailed message to a Microsoft Teams channel and opens a PagerDuty alert routed to the cycle owner so the overrun gets owned and triaged immediately.
When to use it
Use it when scope discipline is a hard commitment, not a suggestion, and a breach genuinely warrants pulling someone in. It fits teams with delivery-date pressure where unbounded mid-cycle additions are treated as a risk to the release.
How it works
- 1A Linear webhook fires when an issue joins the active cycle mid-cycle.
- 2An action step recomputes cumulative points added since the cycle start from Linear.
- 3A logic step checks whether the running total has crossed the configured scope budget.
- 4An action step posts a breach message with the offending additions to Microsoft Teams.
- 5The workflow opens a PagerDuty alert routed to the cycle owner for triage.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.