Automated Launchpad Untriaged Bug Chase List
Every morning, WebRun opens Launchpad, reviews open bugs across your projects, posts a Telegram digest of bugs still untriaged after three days, and texts the project maintainer for any critical-importance bug left untouched for a week, so genuinely urgent reports do not sit buried in the queue.
How do I stop critical bugs from sitting untriaged on Launchpad?
WebRun reviews open Launchpad bugs every morning, posting a Telegram digest of anything still untriaged after three days. Any bug marked critical importance that has gone untouched for a week also gets a direct text to the project maintainer, so routine triage lag stays in the daily digest while a genuinely urgent report gets escalated.
- Untriaged bugs show up in a daily digest instead of quietly aging
- Critical bugs untouched for a week get a direct text instead of waiting
- Community reporters get a faster response because nothing sits forgotten
Built for Open source maintainers · Ubuntu and Canonical ecosystem projects · community project leads · software maintainers
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
launchpad.net/+loginin a real browser with your saved login - no setup, no API keys. -
1
Launchpad - review open bugs
- Open Launchpad and review open bugs across your projects
- Check the triage status and importance of each
- Flag anything untriaged more than three days, and separately any critical bug untouched for a week
Done when Every stale bug is identified with its triage status, importance, and age.
-
2
Telegram - post the untriaged digest
telegram.org
WebRun opens Telegram to post the untriaged digest. - Post the daily digest to the maintainers' Telegram group
- List each bug untriaged more than three days with its title and project
- Include a link to each bug
Done when The maintainers have today's untriaged bug digest in Telegram.
-
3
Twilio - text for critical stale bugs
twilio.com
WebRun opens Twilio to text for critical stale bugs. - Send a text to the project maintainer for any critical bug untouched for a week
- Include the bug title and project
- Keep the message to one line
Done when The maintainer has been texted about every critical bug untouched for a week.
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 WebRun triage or fix the bug itself?
No. It only tracks how long a bug has waited and notifies maintainers. Triaging, assigning importance, and fixing the bug stays entirely with your team.
Why text only for critical bugs?
A routine bug waiting a few days is normal for an open source project. A critical bug untouched for a week is unusual enough to warrant a direct text instead of waiting for the daily digest.
Does it cover community-reported bugs too?
Yes. It checks every open bug regardless of who reported it, which matters for projects that get a lot of external reports.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.