DepMesh: Cross-Team Dependencies

DepMesh brings the SAFe two-end convention to Jira: the issue that NEEDS something (solid border) and the issue that DELIVERS it (dashed border), joined by a curve labeled with the sprint gap. Jira is the source of truth: dependencies are native “Blocks” links and sprints come from the Sprint field, so DepMesh never duplicates your data. Zero data egress — all compute runs inside the Atlassian boundary (Forge), with no external APIs and no third-party analytics. Built for PI Planning: a global ART view (teams x sprints), an Uncommitted column for deliveries without a sprint, plus commitment states and notes. Manage sprints from the board: move issues between sprints by dragging, and create or edit sprints without leaving DepMesh. It respects permissions — reads and writes always happen as the viewing user — and requests only minimal, documented scopes.