analyzing-dependencies

To visualize work-item dependencies and identify blockers, you can map dependency edges across Epics, Sprints, or individual items. The analysis detects circular dependencies and computes critical paths, outputting results as text, Mermaid diagrams, or JSON for integration.

Critical path analysis maps dependency edges across work items to identify the longest sequence of dependent tasks that determines project duration. It helps debug blocked items by highlighting circular dependencies and specific work items causing bottlenecks within an Epic or Sprint.

Yes, you can generate Mermaid diagrams to map circular dependencies in your work items. The analysis constructs a dependency graph for your specified scope and detects cycles, outputting the visual results directly in Mermaid format for easy rendering.

The best way to analyze Epic dependencies and output JSON is to map the dependency edges across the Epic scope and compute the critical paths. The analysis detects blockers and circular dependencies, providing the structural results in JSON format for downstream integration.

Dependency visualization works for individual work items, entire Sprints, and Epics. You can scope the dependency graph construction to a single item to understand its specific relationships and blockers, or expand the analysis to cover the full Sprint.