Automated GitLab Milestone Burndown Tracking
Every Monday, WebRun opens GitLab, checks every active milestone's due date and how many issues and merge requests are still open against it, keeps a calendar reminder on the deadline so it cannot sneak up, and posts the burndown to Microsoft Teams so the whole team sees how much work is left.
How do I track GitLab milestone progress without missing a deadline?
WebRun checks GitLab every Monday for milestones due in the next two weeks, counting the open issues and merge requests against each. It keeps a calendar reminder on every deadline and posts the week's burndown to Microsoft Teams, so a milestone that isn't shrinking fast enough gets noticed before its due date arrives.
- Milestone deadlines stay on the calendar without manual upkeep
- The team sees the burndown trend every Monday, not just at the deadline
- Stuck milestones get flagged while there's still time to react
Built for engineering managers · scrum masters · software development teams · 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
gitlab.com/users/sign_inin a real browser with your saved login - no setup, no API keys. -
1
GitLab - check milestone progress
- Open GitLab and list milestones due in the next 2 weeks
- Count the open issues and merge requests still assigned to each
- Compare this week's open count against last week's
Done when Every upcoming milestone is listed with its open issue and merge request count.
-
2
Google Calendar - keep the deadline on the calendar
calendar.google.com
WebRun opens Google Calendar to keep the deadline on the calendar. - Confirm a reminder exists on each milestone's due date
- Add this week's open issue count to the reminder's description
- Create a new reminder for any milestone that does not have one yet
Done when Every upcoming milestone has a calendar reminder with this week's count attached.
-
3
Microsoft Teams - post the burndown to the team
microsoft.com
WebRun opens Microsoft Teams to post the burndown to the team. - Post the burndown for each milestone to the project channel
- Show whether the open count moved up or down from last week
- Flag any milestone whose open count is not shrinking as its due date nears
Done when The project channel has this week's burndown for every upcoming milestone.
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 issues or move the deadline?
No. WebRun only reports the open count against each milestone. Closing issues or changing a due date is always your team's call.
How far ahead does it look?
Two weeks, so a milestone shows up on the calendar and in the burndown well before its due date arrives.
What if a milestone is stuck?
It flags any milestone whose open issue count is not shrinking week over week as the deadline approaches, so it stands out in Teams.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.