Cross-Team Velocity Chart metrics calculation fixes

In this release, we have fixed an issue in the Cross-Team Velocity Chart when several boards with the same sprint are added to the chart.

Before version 5.8.2, if the same sprint was found more than once, it was processed only once, thus preventing the duplication of scope in the aggregated metrics.

However, it generally leads to the incorrect calculation when two teams work on separate boards in the same sprint while the sprint scope is split between teams using components, labels, or any other “boxes“.

A simple example highlights this case. E.g., sprint scope in Jira has 4 issues:

Open

Open

The Initial commitment of two teams together should be 11 SP. And the configuration of Cross-Team velocity chart for both teams is the following:

However the actual result of aggregated metrics is incorrect - 7 SP, which is sprint scope of Team B only.

What has changed in Velocity Chart v5.8.2

1. the same sprint of both team boards is displayed twice

2. sprint scope is calculated twice to produce aggregated 11 SP in total

3. the name of sprint’s board is added to each sprint item caption

Navigating to each sprint details shows the correct sprint scope for both of the teams.

Team A sprint issues

Team B sprint issues