TICKET MANAGEMENT
Notify every linked ticket when a canonical bug is fixed
When a canonical Linear bug is marked Done, it fans out the resolution to all merged duplicates, suppressed alerts, and linked customer tickets, then posts a fix summary to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerCanonical Linear bug marked DoneLinear
- ActionLoad all linked records from registryPostgres
- ActionClose merged duplicate issuesLinear
- ActionMark signature fixed in releasePostgres
- OutputPost fix summary to SlackSlack
What it does
Closes the loop after a fix ships. When the canonical Linear bug transitions to Done, this flow reads every record that was consolidated under it and notifies each one: closes merged duplicate issues, resolves any held alerts, and replies to affected customer tickets with the fix and release version.
When to use it
After you have been consolidating duplicates into canonical bugs and a fix lands. Use it so nobody who reported or was paged for the crash is left without a resolution, and so the cleanup is automatic rather than manual.
How it works
- 1A Linear webhook fires when a canonical bug moves to Done.
- 2The flow loads all linked records from the Postgres consolidation registry: duplicate issue IDs, suppressed incident keys, and customer ticket IDs.
- 3It closes each merged duplicate Linear issue with a resolved-via-canonical comment.
- 4It updates the registry to mark the signature as fixed in the resolving release.
- 5It posts a Slack summary of the defect, total occurrences, customers affected, and the shipping version.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.