Daily Jira standup digest
A weekday standup digest of overnight Jira activity, posted straight to your team's Slack.
Every weekday at 9am, build a standup digest of what changed on our Jira board in the last 24 hours, then post it to Slack. First, in Jira, run a JQL search for issues updated in the last day on our active board — start from `project = <YOUR_PROJECT_KEY> AND updated >= -1d ORDER BY updated DESC` (swap in your project key, or add `AND sprint in openSprints()` if you run sprints). Pull the status, issue type, assignee, and priority for each. Group what you find into: - "Moved forward" — tickets that changed status (e.g. To Do → In Progress, In Progress → Done), with the key, title, who owns it, and the old → new status. - "In review / waiting" — anything sitting in a review or QA column, so we know what needs eyes today. - "New bugs & blockers" — newly created bugs, or any ticket flagged blocker/highest priority. Call these out first. Then post the digest to Slack using slack_post_message to the #standup channel (swap in your channel). Lead with a one-line headline (e.g. "12 tickets moved, 2 new blockers"), then the three sections as short bullets — each ticket on one line with its key so people can click through. If nothing changed overnight, post a single calm line: "Quiet night — no Jira changes since yesterday." Keep the whole message under a screen and easy to skim on a phone before the meeting.
Standup digest — 30 Jun 2026 12 tickets moved · 2 new blockers · 3 in review 🚨 New bugs & blockers (2) • PAY-418 — Checkout 500s on Safari (new, Highest) — unassigned • PAY-402 — Webhook retries stuck (blocker) — Dana ✅ Moved forward (4 of 9) • PAY-410 — Refund flow → Done — Marcus • PAY-415 — Apple Pay button → In Progress — Priya 👀 In review / waiting (3) • PAY-407 — Rate-limit headers — needs review — Sam
How it works
- It searches Jira with a JQL query for everything updated in the last 24 hours, then sorts it into moved, in-review, and new-bugs/blockers.
- It posts the finished digest straight to your team's channel with Slack — blockers first, every ticket one line with its key to click through.
- Runs at 9:00 AM on weekdays so the summary is waiting in the channel before standup starts.
Make it yours
- Point the JQL at your project key, a specific board, or `openSprints()` so it only watches the work in flight.
- Change the Slack channel, or have it thread the detail under the headline to keep the channel tidy.
- Add an `@here` ping when there's a new blocker, or run it twice a day for fast-moving teams.
Run “Daily Jira standup digest” on autopilot
Copy it to your account, tweak the details, and it runs weekdays at 9:00 am.
Use this routine →More Engineering templates
Each weekday morning, a ranked read-only digest of what threatens your active sprint — blocked, stale, past-due, unassigned, and unestimated work — emailed with keys, owners, and links.
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.
Every Thursday, ask DeepWiki what's new in the public GitHub repos you depend on — releases, breaking changes, and migration notes — emailed as a prioritized summary.