Features

Daily Standup Digest

Auto-generate a pre-standup briefing for your team — surfaces blockers, at-risk PRs, and each developer's current focus.

Overview

Traditional daily standups are status meetings: each engineer repeats what they did yesterday and what they plan to do today. This takes 15–30 minutes and rarely surfaces the information that actually unblocks teams.

Koalr's Daily Standup Digest flips this: it auto-generates a briefing from your connected tools — GitHub, Jira, Linear — and delivers it to your Slack channel 5 minutes before standup starts. Engineers arrive already knowing who is blocked, what is at risk, and what the team shipped yesterday.

Standups become strategic conversations instead of status reports.

What the digest includes

Yesterday's output

  • PRs merged per developer (with title and link)
  • Issues closed / moved to Done in Jira or Linear
  • Deployments that shipped

Today's active work

  • Open PRs per developer (status: in review, needs changes, ready to merge)
  • Issues in-progress per developer

Blockers and at-risk items

  • PRs awaiting review > 24 hours — stuck in the review queue
  • PRs with requested changes, no response > 12 hours — developer hasn't responded to feedback
  • PRs with high deploy risk scores — flagged before they reach production (Deploy Risk)
  • Issues overdue relative to sprint deadline
  • Build failures blocking merge

On-call status

If PagerDuty or OpsGenie is connected:

  • Current on-call engineer (for the day)
  • Any open P1/P2 incidents

Slack message format

📋 *Daily Standup Digest — Platform Team — Mon Mar 16*

*Shipped yesterday:*
• @alice: fix(auth): resolve token refresh race condition (#1234)
• @bob: feat(api): add pagination to /users endpoint (#1231)
• Deployed: api.koalr.com (v2.14.1) ✅

*In flight today:*
• @alice: feat(billing): stripe webhook retry logic — ready to merge ✅
• @bob: fix(ci): flaky test in coverage module — in review ⏳ (23h)
• @carol: feat(reporting): PDF export — in progress 🔨

*Needs attention:*
• ⚠️ @dave's PR #1238 has been waiting review for 31 hours
• 🔴 @eve's PR #1241 has a HIGH deploy risk score (change entropy + DDL migration)
• 🔴 PROD-1047 incident open since 2:34am — @frank on call

*On call today:* @frank

Setting up the digest

  1. Connect GitHub and at least one issue tracker (Jira or Linear) in Integrations
  2. Connect Slack in Integrations → Slack
  3. Navigate to Standup and click Settings
  4. Select:
    • Team — whose activity to include
    • Slack channel — where to post (must be a channel the Koalr Slack app is in)
    • Delivery time — e.g., 9:50 AM (5 minutes before your standup)
    • Timezone — used for "yesterday" / "today" calculation
  5. Click Enable

Configuring content

Click Settings on the Standup page to toggle:

  • Include/exclude deploy risk alerts
  • Include/exclude on-call status
  • Minimum PR wait time before flagging (default: 24h for review, 12h for requested changes)
  • Include/exclude individual developer sections (useful for larger teams)

Disabling for specific periods

The digest respects no-delivery days configured in Settings → Notifications:

  • Weekends (off by default)
  • Company holidays
  • Sprint planning days (manual toggle)

Multiple teams

Configure a separate digest for each team. Each digest posts to a different Slack channel with only that team's activity.

Navigate to Standup to see all configured digests with status (active / paused) and last delivery time.

Relationship to other features

  • WIP Limits — the digest surfaces WIP accumulation as a daily visible signal (WIP Limits)
  • Deploy Risk — high-risk PRs are flagged in the digest before they reach production (Deploy Risk)
  • Incidents — open incidents surface in the digest so the whole team is aware (Incidents)
  • Well-Being Tracker — if a well-being survey is due, the digest includes a Slack survey button (Well-Being Tracker)