Automated Backlog Weekly Issue Scorecard
Every Friday, WebRun opens Backlog, pulls this week's issue counts by status along with the linked commit activity, logs the full scorecard to Google Sheets for the record, and updates the shared status page in Notion so the wider team can see engineering progress without needing a Backlog login.
How do I get a weekly scorecard of Backlog issues and commits?
WebRun checks Backlog every Friday for this week's issue counts by status and linked Git activity, logs the full scorecard to Google Sheets for the record, and updates a shared Notion status page, so stakeholders outside engineering can see weekly progress without needing a Backlog login or waiting on a status update.
- Stakeholders see engineering progress without a Backlog login
- A running weekly scorecard builds up in Sheets
- Issue and commit activity is summarized without manual reporting
Built for Engineering teams · software companies · project managers · product 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
backlog.comin a real browser with your saved login - no setup, no API keys. -
1
Backlog - pull this week's issue and Git activity
backlog.com
WebRun opens Backlog to pull this week's issue and Git activity. - Open the project's issue board
- Count issues opened, closed, and still overdue this week
- Note the linked commits and pull requests
Done when This week's issue and Git activity is fully captured.
-
2
Google Sheets - log the weekly scorecard
google.com
WebRun opens Google Sheets to log the weekly scorecard. - Open the weekly scorecard sheet
- Append this week's counts by status
Done when The sheet has this week's full scorecard logged.
-
3
Notion - update the shared status page
notion.so
WebRun opens Notion to update the shared status page. - Open the shared status page
- Update the summary with this week's opened, closed, and overdue counts
Done when The status page reflects this week's scorecard.
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
Does WebRun close issues or touch the codebase?
No. It only reads issue status and commit history. Closing an issue or pushing code is always done by your engineering team.
Can non-engineers see this without a Backlog login?
Yes. That's the purpose of updating the Notion status page: stakeholders can check progress there without Backlog access.
Does it expose commit content?
No. It only reports commit counts and links already visible in Backlog, not the code changes themselves.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.