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.

Analyzes Jira backlogs weekly to compute a 5-dimension Backlog Health Score. Uses JQL to fetch open issues outside active sprints, detects stale items, orphaned issues, duplicate clusters, blocked chains, and estimation gaps. Generates a Notion grooming brief and Slack digest with top 5 priorities. 26-node n8n workflow with split-workflow scheduler. BQS 12/12 certified.

triggerSchedule01FetcherJira API02Assembler5 BHS Dims03AnalystHealth Score04FormatterBrief + DigestNotionHealth BriefSlackGroom Digest

Four Agents. Weekly Backlog Health Scoring. Per-Issue GROOM Flags.

The Fetcher

Step 1The Fetcher

Code-only

Retrieves backlog issues from Jira Cloud via REST API — all non-sprint issues with creation date, last update, story points, assignee, labels, links, and status. Captures the full backlog snapshot for multi-dimension health analysis.

The Assembler

Step 2The Assembler

Code-only

Computes five Backlog Health Score (BHS) dimensions: staleness (issues untouched beyond threshold), orphans (unassigned + unestimated), duplicates (title/description similarity clustering), blocked chains (blocker dependency analysis), and estimate gaps (issues missing story points).

The Analyst

Step 3The Analyst

Tier 2 Classification

Scores each dimension 1-10, computes composite BHS, classifies backlog health as HEALTHY (≥7), CONCERNING (4-6.9), or CRITICAL (<4). Assigns per-issue GROOM flags indicating which grooming action is needed (ESTIMATE, ASSIGN, DECOMPOSE, CLOSE, DEDUPLICATE).

The Formatter

Step 4The Formatter

Tier 3 Creative

Generates a Notion backlog health brief with dimension breakdowns and per-issue GROOM table, plus a Slack digest with BHS scores, top grooming priorities, and recommended actions.

What It Does NOT Do

×

Does not groom the backlog automatically — it flags issues with GROOM recommendations for human review

×

Does not create or delete Jira issues — this is a read-only analysis tool

×

Does not work with non-Jira tools — this is Jira Cloud-specific (use Linear Backlog Grooming Intelligence for Linear)

×

Does not predict sprint readiness — it scores backlog health independent of sprint planning

×

Does not replace backlog refinement sessions — it provides quantitative inputs for your grooming meetings

The Complete Customer Success Bundle

6 files.

jira_backlog_health_analyzer_v1_0_0.jsonMain workflow (26 nodes)
jira_backlog_health_analyzer_scheduler_v1_0_0.jsonScheduler workflow (3 nodes)
README.md10-minute setup guide
docs/TDD.mdTechnical Design Document
system_prompts/analyst_system_prompt.mdAnalyst prompt reference
system_prompts/formatter_system_prompt.mdFormatter prompt reference

Tested. Measured. Documented.

Weekly 5-dimension backlog health assessment with per-issue GROOM flags and dual-channel delivery (Notion backlog health brief + Slack digest with BHS scores and grooming priorities).

Jira Backlog Health Analyzer v1.0.0──────────────────────────────────────────Nodes:        26 main + 3 scheduler (29 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 backlog analysis)Tool A:       Jira REST API (Basic Auth or OAuth2) — backlog issuesTool B:       Notion (httpHeaderAuth) — backlog health briefTool C:       Slack (httpHeaderAuth) — digest with BHS scores and GROOM prioritiesITP:          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 backlog 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 Backlog Health Analyzer v1.0.0

$199

one-time purchase

What you get:

  • 26-node main workflow + 3-node scheduler
  • Weekly backlog health assessment from Jira backlog data
  • 5-dimension Backlog Health Score (BHS): staleness, orphans, duplicates, blocked chains, estimate gaps
  • BHS 1-10 per dimension with overall health classification (HEALTHY/CONCERNING/CRITICAL)
  • Per-issue GROOM flags: ESTIMATE, ASSIGN, DECOMPOSE, CLOSE, DEDUPLICATE
  • Staleness detection with configurable untouched-days threshold
  • Duplicate clustering by title and description similarity
  • Blocked chain analysis for backlog items with unresolved blockers
  • Estimate gap identification for sprint planning readiness
  • Notion backlog health brief with dimension breakdowns and GROOM table
  • Slack digest with BHS scores and top grooming priorities
  • Configurable: Jira project, staleness threshold, similarity threshold
  • Full technical documentation + system prompts

Frequently Asked Questions

What are the five backlog health dimensions?+

Staleness measures issues untouched beyond a configurable threshold (default 30 days). Orphans identifies unassigned and unestimated issues. Duplicates clusters similar titles and descriptions. Blocked Chains finds backlog items with unresolved dependency chains. Estimate Gaps counts issues missing story points that would be unpredictable in sprint planning.

What are GROOM flags?+

Each flagged issue gets a specific grooming action: ESTIMATE (missing story points), ASSIGN (no assignee), DECOMPOSE (too large or vague), CLOSE (stale with no activity), DEDUPLICATE (similar to another issue). These are prioritized recommendations — your team decides which to act on.

How does this compare to the Linear Backlog Grooming Intelligence?+

Same 5-dimension backlog health taxonomy. The Jira variant uses REST API, handles Jira-specific issue types and custom fields, and maps Jira issue links for blocked chain analysis. 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