TICKET MANAGEMENT
ClickUp stale repro-request follow-up sweep
On a daily schedule, finds bug tasks parked waiting on repro steps, nudges reporters who went quiet, and auto-closes requests that stayed silent past the deadline.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionFetch tasks awaiting repro stepsClickUp
- LogicBucket by days waiting
- ActionPost reminder comment to silent reportersClickUp
- ActionClose tasks past the deadlineClickUp
- OutputPost sweep summary to SlackSlack
What it does
This is the chaser for bugs that were sent back for missing repro steps. Once a day it scans for tickets stuck in the "awaiting repro" state, checks how long they've been waiting, sends a single reminder comment to reporters who haven't replied, and closes out tickets that blew past the response deadline so they stop rotting in the backlog.
When to use it
Use it alongside any intake gate that bounces incomplete bugs. It keeps the "waiting on reporter" column from becoming a graveyard and gives reporters a fair, automated nudge before anything is closed.
How it works
- 1A daily schedule kicks off the sweep.
- 2ClickUp returns all tasks in the awaiting-repro status with their last-comment timestamps.
- 3A logic step buckets each task: recently asked (skip), waiting 3+ days (nudge), or waiting 7+ days (close).
- 4For nudge tasks, the workflow posts a reminder comment tagging the reporter.
- 5For expired tasks, it closes them with a "reopen when you have repro steps" note.
- 6A Slack summary reports how many were nudged and closed.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.