Review workflow connections
Discover global and project workflows and inspect their directed transition graphs. Check coverage warnings: scans are capped at 1,000 workflows and stored finding detail is bounded.
Built for Jira Cloud on Atlassian Forge
Every workflow has a shape. See where it breaks.
Review Jira Cloud workflow structure before your next configuration change. Find unreachable statuses, dead ends, and missing paths to Done, with evidence for each finding. You decide what needs changing.
Free for up to 10 Jira users; paid tiers above 10Read-only analysisJira data stays on Atlassian
Workflow LinterStructural score68/100
0 Critical4 High0 Medium
high
WL007: Status is unreachableNo transition path reaches “Done” from an initial status.
high
WL008: Non-Done status is a dead endIssues can reach “In Progress” but cannot leave it.
high
WL009: No path to completionIssues in “To Do” cannot reach any Done-category status.
high
WL009: No path to completionIssues in “In Progress” cannot reach any Done-category status.
Actual engine results from one synthetic workflow, not customer data or a Jira screenshot. Inspect the example.
Workflow debt is quiet
Broken paths surface when teams can least afford them.
Old statuses remain. Transitions lose their source or target. Teams discover dead ends only after work is blocked. Workflow Linter turns those hidden structures into a clear, prioritized health report.
Separate evidence from intent
Structural findings and design heuristics are labeled clearly. An unreachable status can be a real connection gap; whether it needs changing is still your decision.
Act with evidence
Every finding identifies the status or transition involved and explains why it matters and how to remediate it.
A concrete example
One missing transition. Four high-severity findings.
A simple workflow can look reasonable and still leave active work with no route to completion. Here is how Workflow Linter turns that structural problem into a precise, actionable report.
BeforeHealth score 68
To Do→In Progress×Done
Work can start, but the workflow is missing a transition from In Progress to Done.
WL007Done is unreachable1 finding
WL008In Progress is a non-Done dead end1 finding
WL009No path to Done from To Do or In Progress2 findings
Add one transitionCompleteIn Progress → Done
AfterHealth score 100
To Do→In Progress→Done
After adding the missing Complete transition, every active status has a path to completion.
0 findingsThe four structural findings are resolved.
About this exampleThis uses synthetic workflow data tested with Workflow Linter's local analysis engine. It is not a customer result or an app screenshot. Workflow Linter reports risks but never changes a workflow. A connected path also does not guarantee a user can execute every transition, because Jira permissions, conditions, and validators may still apply.
Ruleset 2026.08.1
Structural checks built for real Jira administration.
Fourteen deterministic rules inspect the paths that matter: how work enters, what can be reached, where it can get stuck, and whether active statuses can reach completion.
No initial transition
CriticalUnreachable status
HighNon-Done dead end
HighNo path to Done
HighGlobal transition needs validator review
ReviewElevated complexity
ReviewImmediate value
From first scan to practical fix in three steps.
Scan
Run an on-demand audit from Jira administration, or let the weekly schedule refresh results automatically.
Understand
See severity, confidence, exact evidence, business impact, and practical remediation for every finding.
Resolve
Fix real defects in Jira or suppress intentional exceptions without changing the underlying workflow.
Transparent Marketplace pricing
Start free. Pay only when the Jira site grows.
The complete product is free for sites with up to 10 users. Larger sites are billed by Atlassian with automatic volume pricing.
Full workflow scans, scheduled refreshes, suppressions, diagnostics, and exports.
Maximum of $20 per month at 100 users. Billing and licensing stay inside Atlassian.
The per-user rate declines at larger tiers. Monthly and annual terms are available through Marketplace.
Pricing is based on the Jira site user tier and is shown before purchase on Atlassian Marketplace.
Runs on Atlassian
Jira configuration stays inside Atlassian.
Workflow Linter runs on Forge, declares no external network egress, and stores only one bounded latest report plus scan status and finding suppressions in installation-scoped storage.
Read-onlyNo Jira mutation calls
Zero egressNo external server, analytics SDK, ads, or AI provider
Minimal scopesWorkflow configuration and app storage only
Bounded retentionOlder successful reports are replaced, not accumulated
Find workflow risk before it blocks work.
Install Workflow Linter for Jira Cloud, run the first read-only scan, and review evidence without sending Jira data to an external service. Free for sites with up to 10 Jira users; larger sites use paid tiers. Review the price and trial terms before installing.