Use proof metrics to understand Jira-connected workflow coverage, evidence, and completion.

Metrics and Readiness

Category: Integrations

Reqflo should make workflow validation measurable.

A journey is not complete simply because it exists. A journey becomes useful when it is linked, mapped, runnable, and supported by recent evidence.

Planning metrics

These metrics show whether Jira work has been connected to executable workflow planning.

Metric	What it shows
Linked Jira work items	Number of Jira issues connected to a journey
Unlinked Jira work items	Jira issues that may need workflow coverage
Imported work items	Jira issues brought into Reqflo for planning
Work items linked to existing journeys	Jira issues connected to already-modeled workflows
Work items without scenarios	Jira issues that have not yet been translated into validation behavior
Work items with scenario coverage	Jira issues that have at least one associated scenario

Coverage metrics

These metrics show whether planned behavior has been mapped to executable validation.

Metric	What it shows
Total scenarios	Number of behaviors identified for a journey
Mapped scenarios	Scenarios connected to request templates or endpoints
Unmapped scenarios	Scenarios that exist but are not executable yet
Total variants	Number of conditions or cases modeled under scenarios
Mapped variants	Variants connected to executable steps
Unmapped variants	Variants that still need implementation
Coverage percentage	Percentage of required scenarios or variants that are executable
Work item coverage	Percentage of linked Jira work items with mapped scenarios

Execution metrics

These metrics show whether workflows actually ran successfully.

Metric	What it shows
Latest run status	Most recent pass/fail result
Pass rate	Percentage of scenarios or variants passing
Failed scenarios	Scenario-level failures blocking completion
Failed variants	Variant-specific failures requiring attention
Run environment	Environment where validation was executed
Run duration	Time required to execute the workflow
Assertion failures	Specific expectations that failed
Response failures	API errors, unexpected statuses, or invalid payloads
Timeout failures	Slow or unavailable dependencies

Evidence metrics

These metrics show whether proof exists and whether it is current.

Metric	What it shows
Evidence available	Whether a journey, scenario, variant, or Jira item has run evidence
Evidence freshness	How recently validation was executed
Evidence link	Direct link to supporting run details
Evidence posted to Jira	Whether results have been sent back to Jira
Last posted status	Most recent Jira-facing validation summary
Stale evidence	Evidence that is too old to support current readiness
Missing evidence	Work that has no supporting run result

Completion metrics

These metrics show whether a workflow is ready for review, release, or follow-up.

Metric	What it shows
Completion percentage	Overall readiness based on linked work, mapping, execution, and evidence
Required scenarios complete	Required behaviors are mapped and passing
Required variants complete	Required cases are mapped and passing
Blocking gaps	Missing mappings, failed runs, or stale evidence
Review readiness	Workflow is ready for QA, product, engineering, or release review
Release readiness	Workflow has sufficient passing evidence for release
Regression readiness	Workflow can be reused for future validation

Recommended workflow status model

Reqflo should make workflow completion explicit.

Status	Meaning
Draft	Journey exists but has no linked work or runnable scenarios
Linked	Jira work items are connected
Scenario-defined	Scenarios have been created
Variant-defined	Important cases have been modeled
Partially mapped	Some scenarios or variants are connected to requests
Mapped	Required scenarios are connected to requests
Runnable	Required inputs and environments are configured
Partially covered	Some required scenarios or variants are runnable
Covered	Required scenarios and variants are runnable
Run complete	Validation has executed
Validated	Latest required run passed
Needs attention	Run failed, mapping is missing, or evidence is stale
Ready for review	Coverage and evidence meet the team's review threshold
Ready for release	Required validation has passed and evidence is current

Example journey summary

Tenant onboarding

Linked Jira items: 3
Scenarios: 9
Mapped scenarios: 7
Variants: 14
Mapped variants: 10
Latest run: Failed
Completion: 78%
Evidence freshness: 2 hours ago
Blocking gaps: 2 unmapped variants, 1 failed scenario

Metrics and readiness