Automated Linear Stalled Issue Chasing
Every morning, WebRun opens Linear, finds issues that have been In Progress or In Review longer than your threshold with no comment or state change, posts each owner a friendly Slack nudge with the issue link, and sends your leads a short Telegram list of everything stuck and how long it has been stuck.
How do I find Linear issues that have stalled mid-cycle?
WebRun chases stalled Linear issues every morning. It scans the active cycle for work sitting In Progress or In Review with no comment or state change past your threshold, sends each assignee one Slack nudge with the links, and posts leads a Telegram list of what is stuck and for how long.
- Stuck issues surface within days, not at cycle review
- Each owner gets one nudge a day, not a stream of pings
- Leads open Telegram to a ranked stuck list every morning
Built for engineering managers · product teams · startup CTOs · delivery leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
linear.app/loginin a real browser with your saved login - no setup, no API keys. -
1
Linear - find issues with no recent update
linear.app
WebRun opens Linear to find issues with no recent update. - Open Linear and filter the active cycle to In Progress and In Review
- Capture issues with no comment, no state change, and no assignee change for longer than your stale threshold
- Note the identifier, title, assignee, estimate, and days since the last activity
Done when Every stalled issue in the active cycle is listed with its owner and days idle.
-
2
Slack - nudge each owner
slack.com
WebRun opens Slack to nudge each owner. - Send each assignee a short Slack message naming their stalled issues and the days idle
- Include the Linear link so a status update is one click away
- Keep it to one message per person per day, however many issues they own
Done when Every owner of a stalled issue has one Slack nudge with their list.
-
3
Telegram - send leads the stuck list
telegram.org
WebRun opens Telegram to send leads the stuck list. - Post a short Telegram summary to the leads group with the stalled count and the oldest offenders first
- Group the list by team so each lead sees their own work
- Call out any issue that has been idle long enough to threaten the cycle end date
Done when Leads have today's stuck list in Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change issue states or reassign work in Linear?
No. WebRun only reads Linear and reports what is idle. Moving an issue, changing its estimate, or reassigning it stays with the humans who own the work.
How long does an issue have to sit still before it counts as stalled?
You set the threshold, commonly two or three working days. WebRun measures from the last comment, state change, or assignee change, so an issue with real activity is never flagged.
Does every teammate get pinged separately?
Each assignee gets one Slack message a day listing all of their stalled issues, so a person with four stuck tickets is nudged once, not four times.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.