TICKET MANAGEMENT
Cluster Linear issues by semantic title similarity
Runs on a schedule, embeds open Linear issue titles and descriptions, groups the ones describing the same root cause.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionFetch all open Linear issuesLinear
- ActionEmbed and cluster by similarityOpenAI
- LogicKeep clusters with 2+ members
- OutputPost merge proposal to Slack for approvalSlack
- ActionExecute approved merge in LinearLinear
What it does
This workflow scans all open Linear issues on a schedule and uses an embedding model to cluster tickets that describe the same underlying problem even when their titles read differently ("login spins forever" vs "auth timeout on sign-in"). For each cluster it drafts a merge proposal naming the suggested canonical issue and the combined subscriber list.
When to use it
Use it when duplicates come from human-filed tickets rather than automated error tooling, so there is no shared fingerprint to key on. The semantic pass catches look-alikes that exact-match rules miss, and the approval step keeps a person in the loop before anything is closed.
How it works
- 1A daily schedule triggers the run.
- 2The flow pulls all open Linear issues with their titles and descriptions.
- 3An OpenAI embedding step vectorizes each issue and clusters by cosine similarity above a threshold.
- 4A branch keeps only clusters with two or more members.
- 5For each cluster it composes a proposed canonical issue and merged subscriber set.
- 6It posts an interactive approval message to Slack; on approve, it executes the merge in Linear.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 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.