Chase changelists before they sit shelved too long
Every morning, WebRun opens Perforce, checks for changelists that have been shelved or left pending for 3 days or more without being submitted, posts a reminder to Microsoft Teams naming the changelist and owner, and creates a Trello card per stale changelist so unsubmitted work doesn't sit forgotten and drift out of sync with everyone else's.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I stop Perforce changelists from sitting unsubmitted?
WebRun checks Perforce every morning for changelists shelved or pending 3 days or more without submitting. It posts a reminder to Microsoft Teams naming the changelist and owner, and creates a Trello card to track it, so unsubmitted work doesn't sit forgotten and drift further out of sync with everyone else's changes.
- Stale changelists get a reminder before they drift further out of sync
- Every pending changelist has a tracked card until submitted
- Work in progress becomes visible instead of sitting invisible in a shelf
Built for game development teams · engineering teams using Perforce · release engineers · platform 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
www.perforce.comin a real browser with your saved login - no setup, no API keys. -
1
Perforce - check for pending changelists
WebRun opens Perforce to check for pending changelists. - Open Perforce and list changelists shelved or pending for 3 days or more
- Capture the changelist number, owner, and description for each
- Skip changelists already carded this run
Done when Every changelist pending 3 days or more is listed with its owner.
-
2
Microsoft Teams - post a reminder to the team
WebRun opens Microsoft Teams to post a reminder to the team. - Post a reminder to the team channel naming each stale changelist and its owner
- Sort by which has been pending longest
- Note which ones already have a Trello card
Done when The team channel has today's list of stale changelists.
-
3
Trello - card each stale changelist
WebRun opens Trello to card each stale changelist. - Create a card for each newly stale changelist with its number and owner
- Move the card to done once it's submitted
- Skip creating a duplicate card for one already tracked
Done when Every stale changelist has a card until it's submitted.
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 submit the changelist itself?
No. WebRun only reports which changelists are pending. Submitting is always a deliberate action your engineer takes.
What counts as stale?
Shelved or pending for 3 days or more without being submitted. Anything submitted within that window never gets carded.
What happens once a changelist is submitted?
Its Trello card moves to done automatically the next time the check finds it's no longer pending.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.