TICKET MANAGEMENT
Nightly sweep that merges stale duplicate bugs into their canonical ticket
Runs on a schedule to scan open Linear bugs, cluster ones sharing a crash signature, close the duplicates with a cross-link to the canonical issue.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionFetch open Linear bugs + signaturesLinear
- LogicCluster by signature, pick canonical
- ActionClose duplicates and cross-link canonicalLinear
- ActionRecord merge decisionsPostgres
- OutputPost consolidation digest to SlackSlack
What it does
A scheduled cleanup pass over your bug backlog. It groups open Linear bugs by their recorded crash signature, picks the oldest as canonical, and closes the rest as duplicates with a comment pointing to the survivor. A Slack digest reports what was merged so triagers can audit it.
When to use it
When duplicates have already accumulated and you want a recurring, hands-off way to keep the backlog clean rather than catching them one event at a time. Pair it with real-time dedup for full coverage.
How it works
- 1A nightly schedule fires the sweep.
- 2The flow pulls all open Linear bugs and their stored signature labels from a Postgres mapping table.
- 3It clusters issues by shared signature and picks the lowest issue number as canonical per cluster.
- 4For each duplicate, it closes the Linear issue as 'Duplicate', comments with the canonical link, and copies any unique reproduction notes upward.
- 5It posts a Slack summary listing each cluster, the canonical ticket, and how many duplicates were folded in.
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
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.