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.

Analyzes completed Jira issues weekly to compute a 5-dimension Velocity Health Score. Parses changelogs for precise cycle time measurement, tracks per-person throughput, identifies component bottlenecks, and monitors bug/feature ratio. Generates dual-audience output: executive summary for leadership and actionable recommendations for engineering. Notion report + Slack digest. 24-node n8n workflow with split-workflow scheduler. BQS 12/12 certified.

triggerSchedule01FetcherJira API02Assembler5 VHD Metrics03AnalystVHS Scoring04FormatterReport + DigestNotionVelocity ReportSlackVHS Digest

Four Agents. Weekly Velocity Report. Dual-Audience Insights.

The Fetcher

Step 1 — The Fetcher

Code-only

Retrieves completed issues from Jira Cloud via REST API across the configurable lookback window — assignees, story points, issue types, resolution dates, labels, and status transition history. Groups data by week for trend comparison.

The Assembler

Step 2 — The Assembler

Code-only

Computes five Velocity Health Score (VHS) dimensions: throughput trend (week-over-week vs 4-week baseline), bottleneck identification (status accumulation analysis), contribution distribution (Gini coefficient for work balance), bug/feature ratio (issue type classification), and cycle time health (median, P90, outliers beyond 3x median).

The Analyst

Step 3 — The Analyst

Tier 2 Classification

Scores each dimension 1-10, computes composite VHS, classifies overall velocity health as HEALTHY (≥7), CONCERNING (4-6.9), or CRITICAL (<4). Produces dual-audience output: executive summary for leadership + engineering recommendations with specific actions. Flags throughput decline >20% as URGENT.

The Formatter

Step 4 — The Formatter

Tier 3 Creative

Generates a Notion weekly velocity report with dimension breakdowns and trend data, plus a Slack digest with VHS scores, executive summary, and top 3 engineering recommendations.

What It Does NOT Do

×

Does not manage sprints or reassign work — this is an analysis tool that reports on completed issue patterns

×

Does not replace engineering retrospectives — it provides quantitative velocity inputs for team discussions

×

Does not work with non-Jira tools — this is Jira Cloud-specific (use Linear Engineering Velocity Reporter for Linear)

×

Does not forecast future velocity — it analyzes historical trends and current health

×

Does not guarantee velocity improvements — it identifies patterns that teams must act on

The Complete Customer Success Bundle

6 files.

jira_engineering_velocity_reporter_v1_0_0.json — Main workflow (24 nodes)
jira_engineering_velocity_reporter_scheduler_v1_0_0.json — Scheduler workflow (3 nodes)
README.md — 10-minute setup guide
docs/TDD.md — Technical Design Document
system_prompts/analyst_system_prompt.md — Analyst prompt reference
system_prompts/formatter_system_prompt.md — Formatter prompt reference

Tested. Measured. Documented.

Weekly 5-dimension engineering velocity analysis with dual-audience output and dual-channel delivery (Notion velocity report + Slack digest with VHS scores and top 3 actions).

Jira Engineering Velocity Reporter v1.0.0──────────────────────────────────────────Nodes:        24 main + 3 scheduler (27 total)Agents:       4 (Fetcher, Assembler, Analyst, Formatter)LLM Calls:    2 per run (Analyst + Formatter)Model:        Sonnet 4.6 (SINGLE-MODEL)Trigger:      Schedule (weekly Monday 8:00 UTC) + WebhookPattern:      BATCH (weekly velocity analysis)Tool A:       Jira REST API (Basic Auth or OAuth2) — completed issuesTool B:       Notion (httpHeaderAuth) — velocity reportTool C:       Slack (httpHeaderAuth) — digest with VHS scores and recommendationsITP:          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 completed 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 Engineering Velocity Reporter v1.0.0

$249

one-time purchase

What you get:

  • ✓24-node main workflow + 3-node scheduler
  • ✓Weekly engineering velocity report from Jira completed issue data
  • ✓5-dimension Velocity Health Score (VHS): throughput trend, bottleneck identification, contribution distribution, bug/feature ratio, cycle time health
  • ✓VHS 1-10 per dimension with overall health classification (HEALTHY/CONCERNING/CRITICAL)
  • ✓Dual-audience output: executive summary for eng leadership + engineering recommendations for the team
  • ✓Throughput decline >20% triggers URGENT alert with root cause analysis
  • ✓Per-week throughput trend with 4-week rolling baseline comparison
  • ✓Contribution distribution via Gini coefficient — detects bus factor risk
  • ✓Bug/feature ratio monitoring with issue type classification
  • ✓Cycle time analysis with median, P90, and outlier detection (>3x median)
  • ✓Notion velocity report with dimension breakdowns and trend data
  • ✓Slack digest with VHS scores and top 3 recommendations
  • ✓Configurable: Jira project, velocity metric (issues/points), baseline weeks, alert threshold
  • ✓Full technical documentation + system prompts

Frequently Asked Questions

What are the five Velocity Health Dimensions?+

Throughput trend (completion rate vs 4-week baseline), bottleneck identification (statuses where issues accumulate), contribution distribution (Gini coefficient measuring work balance), bug/feature ratio (bug-type vs feature-type issues), and cycle time health (median created-to-resolved time plus outlier detection). Each scored 1-10.

What makes this dual-audience?+

The Analyst produces two separate outputs from the same data: an executive summary for engineering leadership (high-level health, trends, strategic concerns) and engineering recommendations for the team (specific bottlenecks, cycle time outliers, action items). The Formatter delivers both in Notion and Slack.

How does this compare to the Linear Engineering Velocity Reporter?+

Identical 5-dimension VHS taxonomy, dual-audience output, and scoring model. The Jira variant uses REST API instead of GraphQL, handles Jira-specific issue types and workflow statuses, and maps Jira resolution data. Choose based on your project management tool.

Is there a refund policy?+

All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions? Contact support@forgeworkflows.com before buying. Full terms at forgeworkflows.com/legal.

Read the full guide →

Related Blueprints

Linear Engineering Velocity Reporter

Weekly AI-generated engineering velocity report from your Linear data — measures throughput trends, identifies bottlenecks, tracks contribution distribution, monitors bug/feature ratio, and flags cycle time outliers.

$199

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.

$199

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.

$249