TICKET MANAGEMENT
Auto-flag duplicate Linear bug reports with a triage comment
When a bug issue is created in Linear, it searches existing issues for the same defect and, on a match.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Linear bug issue createdLinear
- ActionEmbed title + repro stepsOpenAI
- ActionNearest-defect vector searchPostgres
- LogicStrong match and canonical still open?
- ActionSet duplicate relation in LinearLinear
- OutputComment with canonical + overlap reasoningLinear
What it does
Each new Linear bug issue is checked against the existing backlog for the same underlying defect. When a strong match is found, the workflow sets Linear's native duplicate relation, links the canonical issue, and leaves a comment explaining what overlapped so the reporter understands the call.
When to use it
Use it for engineering teams drowning in repeat bug reports for known issues. It keeps the backlog clean without making triagers manually search for prior reports.
How it works
- 1A new Linear issue labeled as a bug triggers the flow.
- 2OpenAI embeds the title and reproduction steps.
- 3Postgres queries stored issue vectors for the nearest defect.
- 4A logic step checks the match score and that the canonical issue is still open.
- 5If matched, Linear marks the new issue as a duplicate of the canonical one.
- 6A comment is posted naming the canonical issue and the overlapping signals; the new vector is saved for future searches.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.