Automated Redmine Overdue Issue Chasing
Every morning, WebRun opens Redmine, finds issues past their due date, archives the full list as a dated file in Google Drive, and texts the project lead the overdue count and top priority issue.
How do I chase overdue Redmine issues automatically?
WebRun checks Redmine every morning for issues past their due date, archives the full list as a dated file in Google Drive, and texts the project lead the overdue count and top priority issue. Overdue work gets tracked daily and surfaced immediately, instead of piling up unnoticed in a busy tracker.
- Overdue issues reach the project lead the same morning by text
- A daily archive shows whether the backlog is growing or shrinking
- Days with nothing overdue generate no unnecessary alert
Built for software teams · IT project managers · open source maintainers · engineering 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
www.redmine.orgin a real browser with your saved login - no setup, no API keys. -
1
Redmine - find overdue issues
WebRun opens Redmine to find overdue issues. - Open Redmine and filter issues across projects to those past their due date
- Note the assignee, tracker, and priority for each
- Skip issues already closed
Done when Every overdue issue is listed with its assignee and priority.
-
2
Google Drive - archive the overdue list
WebRun opens Google Drive to archive the overdue list. - Save today's overdue issue list as a dated file
- File it in the project's Redmine archive folder in Google Drive
- Keep each day's list so trend is visible
Done when Today's overdue list is archived in Google Drive.
-
3
Twilio - text the project lead
WebRun opens Twilio to text the project lead. - Text the project lead the count of overdue issues and the highest priority one
- Keep the message short with just the number and the top issue
- Skip the text if there's nothing overdue
Done when The project lead has today's overdue count by text.
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 close or reassign overdue issues?
No. WebRun only reads due dates and status. It never closes, edits, or reassigns an issue on its own.
Why archive the list every day?
It builds a simple history of overdue counts over time in Google Drive, so you can see whether the backlog is growing or shrinking.
Will the project lead get a text every day even if nothing's overdue?
No, the text only sends when there's at least one overdue issue. An empty day means no message.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.