FLOW
How work moves
Lead time, cycle time, flow efficiency, team touch time, throughput, time in status, and workflow constraints.
Early access
Delivery Diagnostics for Jira
Operational clarity, inside Jira.
A Forge-based Jira Cloud application that turns workflow history into transparent, evidence-based diagnostics about flow, predictability, quality, work mix, constraints, and delivery confidence.
Not another Jira dashboard
Reporting tells you what happened. TDF adds a diagnostic layer.
The goal is not to create more metrics. It is to connect workflow evidence to defined measurements, related signals, measurement confidence, and bounded interpretation.
01
Jira workflow history
02
Defined measurement rules and boundaries
03
Related delivery signals and trends
04
Measurement confidence and evidence context
05
Diagnostic interpretation and investigation guidance
One connected view of delivery health.
Selected TDF diagnostics are implemented where delivery work already lives, while the wider framework remains the source of diagnostic intent.
PREDICTABILITY
How consistently it moves
Variation, historical patterns, throughput stability, trends, delivery pressure, and predictability risk.
QUALITY / WORK MIX
What pressure surrounds delivery
Defect and quality patterns alongside the composition of completed work and configured classifications.
CONFIDENCE
What can be interpreted safely
Flow Health, Delivery Confidence, measurement coverage, and evidence context that qualify how strongly results should be read.
Measurement confidence by design
Can I trust this measurement?
A metric should not look equally trustworthy in every context. TDF keeps results connected to workflow configuration, data coverage, measurement boundaries, flow-start evidence, and fallback conditions.
Delivery Confidence describes what the delivery signals collectively suggest. Measurement Confidence describes how much the underlying evidence deserves to be trusted.
Measurement contextIllustrative dataEvidence: sufficient
Flow health69Watch
Predictability74%moderate
Measurement confidenceStrongcoverage sufficient
Primary constraintReviewpersistent queue
What Jira can—and cannot—tell us about value.
Protecting this boundary is part of making diagnostics trustworthy.
SUPPORTED BY WORKFLOW EVIDENCE
Work composition
TDF can describe completed work by configured issue classifications, defects, operational demand, and other work-mix evidence available in Jira.
REQUIRES OUTCOME EVIDENCE
Realised business value
A completed Jira item does not prove customer adoption, revenue, satisfaction, or another business outcome. TDF should only make those claims when appropriate outcome evidence is explicitly connected.
Designed for trust.
The implementation follows the same principles as the framework.
DATA
Built on Atlassian Forge
Core diagnostics are designed to operate in the Atlassian ecosystem without requiring an external analytics warehouse.
EVIDENCE
Traceable by design
Measurements remain connected to source context, definitions, configuration, and the evidence conditions behind interpretation.
PEOPLE
Never a productivity scorecard
TDF measures delivery systems. It does not rank individuals or turn team delivery evidence into performance league tables.
Early access
Current availability
Validation before broader availability.
TDF Delivery Diagnostics for Jira is currently in early access. The product is being validated with selected teams to strengthen calculation integrity, measurement confidence, diagnostic usefulness, and decision support before broader availability.