TICKET MANAGEMENT
Detect re-pointed Linear issues mid-cycle and alert Slack
Catches issues whose estimate is raised after the cycle starts, a quieter form of scope creep than new tickets, and alerts a Slack channel with the old and new points.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue update webhookLinear
- LogicIssue is in the active, started cycle
- LogicEstimate increased from previous value
- ActionFetch change actor and issue context from LinearLinear
- OutputPost estimate-inflation alert to SlackSlack
What it does
This workflow watches for estimate changes on issues that already belong to the active cycle. When someone bumps an issue from 2 points to 5 after the cycle has begun, that is hidden scope growth on committed work, and this catches it. It posts a Slack alert showing the issue, the old estimate, the new estimate, and who changed it.
When to use it
Use it when your team mostly respects new-ticket discipline but estimates quietly balloon as work reveals complexity. It is the right guard when total cycle capacity matters more than ticket count, since re-pointing can blow a commitment without adding a single issue.
How it works
- 1A Linear webhook fires on issue update events.
- 2A logic step confirms the issue is in the currently active, already-started cycle.
- 3A logic step checks whether the estimate field actually increased between the previous and new values.
- 4An action step reads the change actor and surrounding issue context from Linear.
- 5The workflow posts an estimate-inflation alert to Slack with the point delta highlighted.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
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.