Automated Assembla Overdue Ticket Chase List
Every Monday, WebRun opens Assembla, reviews open tickets across your spaces, finds any untouched for more than two weeks, saves a report to Google Drive, and posts a Slack chase list so old tickets get a decision instead of sitting open indefinitely.
How do I find Assembla tickets that nobody has touched in weeks?
WebRun reviews open Assembla tickets every Monday, finds any untouched for 14 days or more, and saves a dated report to Google Drive. It then posts a Slack chase list grouped by assignee, so tickets that have gone quiet get a decision, a close, or a reassignment instead of sitting open indefinitely.
- Old tickets get a weekly nudge instead of quietly aging for months
- Each assignee sees exactly which of their tickets have gone quiet
- A dated history in Drive shows whether the backlog is improving
Built for Software development teams · project managers · engineering leads · outsourced dev 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
app.assembla.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Assembla - find untouched tickets
- Open Assembla and review open tickets across your spaces
- Check each ticket's last activity date
- Flag any ticket with no comment or status change in the last 14 days
Done when Every ticket untouched for 14 days or more is identified with its assignee.
-
2
Google Drive - save the ticket report
drive.google.com
WebRun opens Google Drive to save the ticket report. - Open the Assembla Reports folder in Google Drive
- Save a dated report listing every untouched ticket with its assignee and last activity date
- Keep the prior four weekly reports for comparison
Done when A dated report of untouched tickets is saved in Google Drive.
-
3
Slack - post the chase list
slack.com
WebRun opens Slack to post the chase list. - Post the chase list to the team's Slack channel
- Group untouched tickets by assignee
- Ask each assignee to update, close, or reassign their tickets
Done when The team has this week's chase list of untouched Assembla tickets in Slack.
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 close or reassign tickets itself?
No. It only builds the chase list. Closing, reassigning, or updating any ticket stays a decision for the assignee.
What counts as untouched?
No comment, status change, or update in the last 14 days. That window can be adjusted to match how your team works.
Does it only cover one project?
No. It checks every space you give it access to, so the chase list can span multiple projects in one weekly post.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.