Daily Jira sprint risk report
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.
Weekdays at 9:00 AMEngineering Emailed to you
Use this routine →Opens prefilled — review and save.
Works with
The instructions
Every weekday at 9am, read the active sprint via JQL and email a ranked, read-only risk report. Do not comment on, transition, edit, or create any issue — this is a digest only. 1. Resolve which projects and sprint are visible to me with the visible-projects lookup, then search the active sprint with JQL: `Sprint in openSprints() AND project = <my project>`. If I have several active sprints, cover each under its own heading. 2. From that result set, flag issues by risk signal using issue fields (not comment bodies): blocked or flagged work (a Blocked status, a Flagged/Impediment flag, or an "is blocked by" link — whichever my workflow uses); stale items with no update in ~3 days (`updated <= -3d`); past-due items (`duedate < endOfDay()`); unassigned stories (`assignee is EMPTY`); and unestimated stories (`"Story Points" is EMPTY`). Also surface likely scope creep — items that appear to have been added mid-sprint (e.g. created after the sprint started); treat this as approximate, not exact. 3. Rank findings by risk to the sprint goal (blocked and past-due first, then stale, then unassigned/unestimated, then scope creep). For each issue include the key (e.g. PROJ-123), summary, status, assignee (or "unassigned"), the signal that flagged it, and a direct link built from the site base URL and the key. 4. Lead the email with a one-line headline: total at-risk issues and the single most pressing one. Keep it tight and skimmable — group by signal, no walls of text. 5. Rely on issue fields rather than reading comment streams (media-heavy tickets can hang). If a JQL search returns nothing, or a field like Story Points isn't configured in my instance, say so plainly instead of guessing — e.g. "no blocked issues found" or "Story Points field not detected." Stay strictly read-only throughout.
What a run emails you
Sprint risk — PAY board, Tue 30 Jun 2026 7 issues at risk; PAY-418 is blocked AND past due — payout reconciliation may slip the goal. Blocked / flagged (2) - PAY-418 Reconcile failed payouts — In Progress · Maya R. · flagged "waiting on vendor API" · due 29 Jun (overdue) → /browse/PAY-418 - PAY-431 Refund webhook retries — To Do · Devin O. · "is blocked by" PAY-405 → /browse/PAY-431 Past due (1) - PAY-402 Add idempotency keys — In Progress · Sara L. · due 27 Jun → /browse/PAY-402 No update in 3+ days (2) - PAY-377 Settlement export — In Review · Tom K. · last updated 26 Jun → /browse/PAY-377 - PAY-390 Currency rounding fix — To Do · unassigned · last updated 25 Jun → /browse/PAY-390 Unassigned / unestimated (1) - PAY-440 Dispute status sync — To Do · unassigned · no Story Points → /browse/PAY-440 Likely added mid-sprint (1) - PAY-447 Fraud-flag banner — created 29 Jun (sprint started 23 Jun) → /browse/PAY-447
How it works - Attach your **Jira** connection — this routine only needs read access. It searches your active sprint with JQL and reads issue fields; it never comments, transitions, edits, or creates anything (those are a separate write permission you don't grant here). - It ranks by *risk to the sprint goal*, not just recency: blocked or flagged work and past-due items surface first, then stale tickets with no update in ~3 days, then unassigned/unestimated stories, then likely scope creep. - Keep **"Email me the result"** on to get the digest in your inbox each morning before standup — a tight, skimmable list with keys, owners, and direct links.
Make it yours - Tell it how *your* team models "blocked" — a Blocked status, a Flagged/Impediment flag, an "is blocked by" link, or a label — since Jira has no universal field for it. - Adjust the staleness window (e.g. "no update in 2 days") or the project/sprint scope, and name your Story Points field if it's custom-named in your instance. - Change the cadence or send time, or split into per-project sections if you run several active sprints.
Your connections stay yours: tokens are encrypted at rest, and the agent only uses the access you grant.
Run “Daily Jira sprint risk report” on autopilot
Copy it to your account, tweak the details, and it runs weekdays at 9:00 am.
Use this routine →More Engineering templates
Daily Jira standup digestEngineering
A weekday standup digest of overnight Jira activity, posted straight to your team's Slack.
Weekdays at 9:00 AM
Weekly Cloudflare docs & feature digestEngineering
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.
Fridays at 9:00 AM
Weekly library version & migration digestEngineering
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.
Mondays at 8:00 AM
W
Weekly GitHub repo changelog digestEngineering
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.
Thursdays at 9:00 AM