Jira Release Risk Assessor
AI-powered pre-release risk assessment — open blockers, completion ratio, test coverage gaps, dependency risk, and scope stability scored with GO/CONDITIONAL GO/NO-GO recommendation.
Assesses Jira fix version readiness before release. Analyzes open blockers, completion ratios, untested issues, external dependency risks, and late scope additions. Produces GO/CONDITIONAL GO/NO-GO recommendation with blocker veto enforcement. Notion release risk brief + Slack go/no-go summary. 25-node n8n workflow with optional scheduler. Blueprint Quality Standard (BQS) 12/12 certified. We built this after a release shipped with two unresolved blockers that were marked as "in progress" but never completed. The assessor checks release readiness against configurable criteria and flags gaps before the release train leaves.
Last updated March 18, 2026
Post-mortems are written for 30% of incidents, and release risk assessments happen informally if at all. The institutional knowledge from past incidents sits in documents nobody re-reads. Automated incident analysis and release risk scoring makes that knowledge operational — surfacing relevant past incidents when similar patterns emerge.
Four Agents. Per-Release Assessment. GO/NO-GO Recommendation.
Step 1 — The Fetcher
Code-only
Triggered by webhook when a fix version is created or updated in Jira. Retrieves all issues linked to the release version — statuses, blockers, test coverage indicators, dependencies, and scope changes since version creation.
Step 2 — The Assembler
Code-only
What does The Assembler actually decide? Computes five Release Risk Score (RRS) dimensions: open blockers (unresolved Critical/Blocker issues), completion ratio (done vs total issues), test coverage (issues with linked test cases), dependency risk (cross-project issue links), and scope stability (issues added/removed after version creation).
Step 3 — The Analyst
Tier 2 Classification
This step exists because raw data alone is not enough. Scores each dimension 1-10, computes composite RRS. Applies blocker veto: any open Critical/Blocker forces NO-GO regardless of composite score. Classifies release readiness as GO (RRS ≥7, no blockers), CONDITIONAL GO (RRS 4-6.9, conditions listed), or NO-GO (RRS <4 or blocker veto). Lists specific conditions for CONDITIONAL releases.
Step 4 — The Formatter
Tier 3 Creative
Without this step, upstream analysis sits idle. Generates a Notion release risk assessment page with dimension breakdowns, blocker details, and GO/NO-GO recommendation, plus a Slack digest with the release verdict, RRS scores, and blocking issues if any.n8n's batch node only outputs the last iteration. Without explicit accumulation in static data, multi-record pipelines silently drop results.
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 block releases in Jira — it provides a recommendation that humans act on
Does not run automated tests — test coverage is inferred from linked test case issues, not from CI/CD
Does not work with non-Jira tools — this is Jira Cloud-specific
Does not predict production incidents — it assesses pre-release readiness based on issue data
Does not manage fix versions — this is a read-only analysis tool
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.
Per-release 5-dimension risk assessment with blocker veto and GO/CONDITIONAL GO/NO-GO recommendation, delivered via Notion release assessment page and Slack digest.
Tested on n8n v2.7.5, March 2026
Jira Release Risk Assessor v1.0.0──────────────────────────────────────────Nodes: 25 main + 3 scheduler (28 total)Agents: 4 (Fetcher, Assembler, Analyst, Formatter)LLM Calls: 2 per run (Analyst + Formatter)Model: Sonnet 4.6 (SINGLE-MODEL)Trigger: Webhook (fix version) + SchedulePattern: BATCH (per-release assessment)Tool A: Jira REST API (Basic Auth or OAuth2) — fix version issuesTool B: Notion (httpHeaderAuth) — release risk assessment pageTool C: Slack (httpHeaderAuth) — digest with GO/NO-GO verdictITP: 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 assessment + 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 fix versions
- ▪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 Release Risk Assessor v1.0.0
$199
one-time purchase
What you get:
- ✓25-node main workflow + 3-node scheduler
- ✓Per-release risk assessment from Jira fix version data
- ✓5-dimension Release Risk Score (RRS): open blockers, completion ratio, test coverage, dependency risk, scope stability
- ✓RRS 1-10 per dimension with GO/CONDITIONAL GO/NO-GO recommendation
- ✓Blocker veto: any open Critical/Blocker forces NO-GO regardless of composite score
- ✓CONDITIONAL GO includes specific conditions that must be met before release
- ✓Cross-project dependency risk identification via Jira issue links
- ✓Scope stability tracking (issues added/removed post-version creation)
- ✓Notion release risk assessment page with dimension breakdowns and blocker details
- ✓Slack digest with release verdict, RRS scores, and blocking issues
- ✓Webhook-triggered: fires on fix version creation/update or on schedule
- ✓Full technical documentation + system prompts
Frequently Asked Questions
What is the blocker veto?+
If any issue with priority Critical or Blocker is unresolved in the release version, the recommendation is automatically NO-GO regardless of the composite RRS score. This is a hard constraint — the blocker must be resolved or removed from the version before the release can be assessed as GO.
What triggers the assessment?+
Two trigger modes: (1) Webhook from Jira when a fix version is created or updated — for on-demand pre-release checks. (2) Scheduled via the scheduler workflow — for recurring release readiness monitoring. Both modes analyze the same fix version data.
What does CONDITIONAL GO mean?+
RRS between 4 and 6.9 with no open blockers. The Analyst lists specific conditions: for example, "3 issues in Testing status must pass QA" or "dependency on PROJECT-X release must be confirmed." The release can proceed if those conditions are met before the release window.
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 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.
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.