TICKET MANAGEMENT
Generate a Linear cycle-end scope retrospective in Notion and announce it on Discord
When a cycle closes, builds a scope retrospective page in Notion covering committed vs delivered, every mid-cycle addition with its owner, and completion rate.
How it runs
The automated pipeline, trigger to output.
- TriggerCycle-end schedule fires
- ActionPull commitment snapshot and final issue set from LinearLinear
- LogicCompute additions, completion rate, and per-person scope
- ActionCreate scope retrospective page in NotionNotion
- OutputPost retro summary and link to DiscordDiscord
What it does
At cycle close, this workflow assembles a full scope retrospective. It pulls the cycle's commitment snapshot and final state, lists every issue added after planning along with who added it, and computes committed-versus-delivered points and completion rate. It writes all of this to a structured Notion page, then posts a short summary plus the page link to Discord so the retro is ready before the meeting.
When to use it
Use it when scope-creep alerts during the cycle are not enough and you want a permanent record per cycle to spot patterns over time. It is ideal for teams that run formal retrospectives and want the scope section pre-written and evidence-backed.
How it works
- 1A scheduled or cycle-completion trigger fires when the active cycle ends.
- 2An action step pulls the cycle's commitment snapshot and final issue set from Linear.
- 3A logic step computes additions, completion rate, and per-person scope contributions.
- 4An action step creates a structured retrospective page in Notion.
- 5The workflow posts the summary and Notion link to Discord.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 3Connect DiscordCommunity channels + voice + bots.
- 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.