Issue Summary

'Story Points' was selected as the 'Estimation Statistic' Board Settings.

The Old Board/Backlog view and the Enhanced Board/Backlog View have different Story Points counts per Issue Category even though the Total Story Points counts are the same.

As per the Board Colum Configuration documentation :

• If the issue is in one of the statuses that were mapped to the first board column, then add its story points to the Gray color sum.
• If the issue is in one of the statuses that were mapped to the last board column, then add its story points to the Green color sum.
• Else, if the issue is in one of the statuses mapped to any other columns (excluding the first column and the last one) then add its story points to the Blue color sum.

In the Old Board/Backlog view, the Story Points are calculated based on the above colour coding. So, we see 10 Story Points in grey and 2 Story Points in Blue:

However, when we enable the Enhanced Board/Backlog view, the Story Points are calculated based on the Issue Status category (not the previous behaviour as documented above). We see 0 story points in Grey and 12 Story Points in Blue. This is not documented in the Public Blog for the new changes.

Steps to Reproduce

1. Create a Scrum Board in the company-managed Project.
2. In the Board setting, column mapping, select any of the statuses (Eg: Un-done as above) with 'In progress' status category in the left-most column.
3. Select 'Story Points' as the 'Estimation Statistic' on Board Settings
4. Create a Task/Story with Story Points, and move the issue to the status from Step 2.

When the Old Backlog/Board view is used, the Story Points for this issue is counted in the Grey colour:

When the Enhanced Board/Backlog is enabled, the Story Points for this Issue are counted in the Blue colour category:

Expected Results

The Old Board/Backlog view and the Enhanced Board/Backlog View should display the same Story Points count per Issue Category.

Actual Results

When we enable the Enhanced Board/Backlog view, the Story Points are calculated based on the Issue Status category (not the previous behaviour as documented above)

Workaround

No workaround is available at this time.