Jira Epic Completion Forecaster
AI-powered weekly epic completion forecasting — velocity trends, resource bottlenecks, scope stability, and estimate confidence scored with ON TRACK/AT RISK/OVERDUE traffic light per epic.
Forecasts Jira epic completion dates weekly using per-epic velocity analysis. Computes remaining work, weekly throughput, projected completion dates, and variance from due dates. Identifies resource bottlenecks, scope instability, and estimate gaps. Generates per-epic traffic light classification with prioritized recommendations. Notion dashboard + Slack digest. 27-node n8n workflow with Wednesday scheduler. Blueprint Quality Standard (BQS) 12/12 certified. This came from a PM who was asked "when will this epic ship?" and answered with a guess. The forecaster uses actual velocity data and remaining scope to project completion dates with confidence intervals.
Last updated March 18, 2026
Product backlogs grow 3-5x faster than engineering capacity can address them. Without systematic grooming, stale tickets accumulate, priority rot sets in, and sprint planning becomes a negotiation exercise rather than a data-driven process. Automated backlog health analysis surfaces what needs attention before planning day.
Four Agents. Weekly Epic Forecasting. Per-Epic Traffic Lights.
Step 1 — The Fetcher
Code-only
Retrieves active epics and their child issues from Jira Cloud via REST API — story points, statuses, assignees, sprint membership, completion dates, and historical velocity data per epic. Captures progress snapshots for trend analysis.
Step 2 — The Assembler
Code-only
What does The Assembler actually decide? Computes four Epic Health dimensions per epic: velocity trend (recent completion rate vs historical baseline), resource bottlenecks (assignee workload distribution), scope stability (child issues added/removed over time), and estimate confidence (ratio of estimated vs unestimated child issues).
Step 3 — The Analyst
Tier 2 Classification
This step exists because raw data alone is not enough. Classifies each epic as ON TRACK (velocity stable, scope stable, resources balanced), AT RISK (declining velocity, scope creep, or resource bottleneck), or OVERDUE (past target date or velocity insufficient to complete on time). Generates per-epic completion probability and recommended interventions.
Step 4 — The Formatter
Tier 3 Creative
Without this step, upstream analysis sits idle. Generates a Notion epic forecast dashboard with per-epic traffic lights, dimension breakdowns, and intervention recommendations, plus a Slack digest with the epics requiring attention and their specific risk factors.A non-idempotent re-run turned a 32-node workflow into 44 nodes. Every build script now removes existing nodes before adding fresh ones.
That's the full pipeline. Here's what it intentionally does NOT do — and why those boundaries exist.
What It Does NOT Do
Does not manage epics or reassign work — this is an analysis tool providing forecast signals
Does not replace roadmap planning tools — it forecasts completion, not prioritization
Does not work with non-Jira tools — this is Jira Cloud-specific
Does not guarantee accurate forecasts — predictions are based on historical velocity patterns
Does not modify epic target dates — it reports against existing dates or inferred timelines
With those boundaries clear, here's everything that ships when you purchase.
The Complete Customer Success Bundle
7 files.
The technical specifications below are ITP-measured, not estimated.
Tested. Measured. Documented.
Weekly per-epic completion forecasting with traffic light classification, 4-dimension health analysis, and dual-channel delivery (Notion epic dashboard + Slack digest with at-risk epics).
Tested on n8n v2.7.5, March 2026
Jira Epic Completion Forecaster v1.0.0──────────────────────────────────────────Nodes: 27 main + 3 scheduler (30 total)Agents: 4 (Fetcher, Assembler, Analyst, Formatter)LLM Calls: 2 per run (Analyst + Formatter)Model: Sonnet 4.6 (SINGLE-MODEL)Trigger: Schedule (weekly Wednesday 9:00 UTC) + WebhookPattern: BATCH (weekly epic forecast)Tool A: Jira REST API (Basic Auth or OAuth2) — epics + child issuesTool B: Notion (httpHeaderAuth) — epic forecast dashboardTool C: Slack (httpHeaderAuth) — digest with at-risk epicsITP: 8/8 records, 14/14 milestonesBQS: 12/12 PASSCost: $0.03–$0.10 per run
What You'll Need
Platform
n8n 2.7.5+
Est. Monthly API Cost
~$0.03-0.10 per weekly run + Jira subscription.
Credentials Required
- ▪Anthropic API
- ▪Jira Cloud API (Basic Auth or OAuth2)
- ▪Slack (Bot Token, httpHeaderAuth Bearer)
- ▪Notion (httpHeaderAuth Bearer)
Services
- ▪Jira Cloud with epics and child issues
- ▪Anthropic API key
- ▪Notion workspace
- ▪Slack workspace (Bot Token with chat:write)
Setup Track
Quick Start
~15 min
All credentials live, n8n running
Full Setup
1–2 hrs
Needs API config + tables
From Scratch
2–4 hrs
No n8n, no credentials
Jira Epic Completion Forecaster v1.0.0
$249
one-time purchase
What you get:
- ✓27-node main workflow + 3-node scheduler
- ✓Weekly epic completion forecasting from Jira epic and child issue data
- ✓4-dimension Epic Health analysis: velocity trend, resource bottlenecks, scope stability, estimate confidence
- ✓Per-epic traffic light classification: ON TRACK / AT RISK / OVERDUE
- ✓Completion probability estimation based on velocity trend and remaining scope
- ✓Resource bottleneck detection per epic with assignee workload analysis
- ✓Scope stability tracking showing child issue additions and removals over time
- ✓Estimate confidence scoring for sprint planning readiness
- ✓Notion epic forecast dashboard with per-epic traffic lights and dimension breakdowns
- ✓Slack digest with AT RISK and OVERDUE epics and recommended interventions
- ✓Configurable: Jira project, epic filter, velocity baseline period
- ✓Full technical documentation + system prompts
Frequently Asked Questions
What do the traffic light classifications mean?+
ON TRACK: velocity is stable or improving, scope is stable, resources are balanced, and the epic is projected to complete on time. AT RISK: one or more dimensions are declining — velocity drop, scope creep, or resource bottleneck detected. OVERDUE: past the target completion date, or current velocity is insufficient to complete remaining work on time.
How does it calculate completion probability?+
Based on the ratio of remaining story points to the 4-week rolling velocity for that epic, adjusted by scope stability (if scope is growing faster than completion, probability decreases). Epics without story point estimates get a confidence penalty.
Can it forecast for specific epics only?+
Yes. Configure the EPIC_FILTER in the scheduler to target specific epic keys, labels, or components. By default, it analyzes all active epics (status not Done) in the configured project.
Is there a refund policy?+
All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions?
Related Blueprints
Jira Sprint Risk Analyzer
AI-powered weekly sprint risk assessment — velocity deviation, blocked chains, scope creep, and concentration risk scored across 4 dimensions with per-issue flags.
Jira Engineering Velocity Reporter
AI-powered weekly engineering velocity intelligence — throughput trends, bottlenecks, contribution balance, bug/feature ratio, and cycle time health scored across 5 dimensions with dual-audience output.
Jira Backlog Health Analyzer
AI-powered weekly backlog health assessment — staleness, orphans, duplicates, blocked chains, and estimate gaps scored across 5 dimensions with per-issue GROOM flags.