Meet the new BigPicture navigation
A faster, smarter, and more intuitive way to work is here. We’ve redesigned BigPicture navigation to give you a smoother experience and better access to what matters most.
→ Discover what’s new, explore key improvements, and review feature name updates on the New navigation page.
→ The rollout will happen gradually, and the previous navigation will be retired in September 2026.
Cross-team dependencies report
About the Cross-team dependencies report
The Cross-team dependencies report lets you identify project areas handled by two different teams, where coordination of work can be crucial.
The Cross-team dependencies report is in the form of a matrix and presents the names of projects or iterations that:
are assigned to a given program or project
have at least one incoming or outgoing dependency (note - both dependency tasks must be open).
The intersection of the matrix's rows and columns shows the number of cross-team dependencies in the entire project (including iterations).
The more dependencies, the color changes from green to yellow to red.
If a team is not allocated to the Box or has no dependencies, it will not be shown in the report.
If there are no cross-team dependencies between Boxes, the report will present "No data."
Contrary to the Dependencies report:
This report displays parent-child dependencies (marked as CP).
This report does not present dependencies between tasks of the same team (in the fields on the matrix diagonal).
When you click the report field, you will see detailed information about each dependency (divided into inbound and outbound dependencies).
The report presents soft dependencies (S) and strong dependencies (SE, EE, ES, SS).
The digits between the team names indicate the number of dependencies.
Status is abbreviated:
Report configuration
You can rename your report using the report configuration.
Export
BigTemplate addon is required.
You can export information of a given cell into .xlsx.
The file is a flat list (items are grouped per Team). The following information on both the source and target tasks of a dependency:
Team name
task key
task status
summary
dependency type