Cross-Team Collaboration Index(4.5.7)

Collaboration leaves little direct trace in Jira events. What they do record is co-occurrence: two people generating events on the same issue, whatever the events were. This index quantifies that overlap and nothing more—it does not see reviews, conversations or meetings, and a bulk status change by one person over many issues counts as overlap with everyone who touched those issues. Read it as a map of whose issues overlap, within and between projects.

What you can conclude

• Actor pairs with high overlap touch the same issues often—a working relationship, a dependency, or a triage role that touches everything; the matrix cannot tell these apart.
• Actors with low overlap across the board touch issues nobody else touches—worth asking whether that is a specialist role or a silo.
• A sparse matrix across a large team is consistent with work being divided rather than shared—worth considering for cross-functional projects.

How this chart works

Matrix showing, for each pair of actors, the share of the less active actor's issues that both generated events on: the pair's shared issues divided by the smaller of the two actors' issue counts, so a 100 means one actor's every issue was also touched by the other. With no project selected the share is pooled across every project the pair shares; under the project filter it is that project's own. A pair is rated only when the base is at least ten issues; below ten one shared issue would move the figure by ten points or more, so the cell is blank rather than a percentage. Higher values indicate more frequent joint working. Pairs that include an account Jira reports as an app, such as Automation for Jira, or as a service-desk customer are left out; accounts Jira returned no type for stay in and are labeled unknown. The percentages count every issue in the full retained event history, so this is an all-time collaboration profile: the page's date range does not narrow this visual. Use the project filter to focus on specific teams.