Automated Jira Blocker Escalation
Every hour, WebRun opens Jira, finds blocker and highest-priority issues that are unassigned or have had no update inside your response window, records each one in an Airtable escalation register, and texts the on-call lead through Twilio so a blocker never sits all day without an owner.
How do I get alerted when a Jira blocker has no owner?
WebRun checks Jira every hour for blocker and highest-priority issues that are unassigned or have gone quiet past your response window. It logs each one in an Airtable escalation register and texts your on-call lead through Twilio, so a critical issue never sits an entire day without an owner.
- Blockers get an owner within the hour instead of by end of day
- Every escalation is timestamped in Airtable for later review
- The on-call lead is texted only when something is genuinely stalled
Built for engineering managers · delivery leads · support engineering · on-call teams
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
id.atlassian.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Jira - find unowned blockers
atlassian.com
WebRun opens Jira to find unowned blockers. - Open Jira and filter to open issues at blocker or highest priority in your active projects
- Capture the issue key, summary, project, assignee, and time since the last update
- Keep only the issues that are unassigned or have had no update inside your response window
- Skip issues already escalated in the last few hours so the same blocker is not raised repeatedly
Done when Every unowned or stalled blocker is listed with its key, project, and time since last update.
-
2
Airtable - log the escalation
airtable.com
WebRun opens Airtable to log the escalation. - Open your escalation register in Airtable
- Add a row per blocker with the issue key, the project, the reporter, and how long it has been stalled
- Set the escalation status to Raised and stamp the time
- Update the existing row instead of adding a new one when the same issue is still open
Done when Airtable holds a current, timestamped row for every raised blocker.
-
3
Twilio - text the on-call lead
twilio.com
WebRun opens Twilio to text the on-call lead. - Compose a short text naming each blocker, its project, and how long it has been unowned
- Send it only to the numbers on your saved on-call roster
- Queue the message unsent for approval if a recipient is not on that roster
- Send nothing at all when the blocker list is empty
Done when The on-call lead has this hour's blocker text, or no text was needed because nothing was stalled.
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
Can it text someone outside my team?
No. Texts go only to the on-call roster you save at setup. A message aimed at any other number is queued unsent for a human to approve, so no customer or stranger is ever texted.
Will it reassign or close Jira issues?
No. WebRun reads Jira and never edits an issue, changes an assignee, or moves a status. Deciding who picks up a blocker stays with your team.
How do I stop the same blocker texting me every hour?
Each issue is escalated once, then tracked in the Airtable register. It only texts again if the issue is still unowned after the quiet window you set, usually a few hours.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.