要約

Board column configuration changes can cause discrepancy in the Reports. For example: 

• The issues completed in the previous sprint will show up in the next sprint, with 0 story points. 
• The Story points commitment in the Velocity chart might differ from the Story points in the Sprint Report 
  
  

環境

Jira Cloud

診断

Consider the below configuration for explanation purposes: 

• Board Configuration: To Do, In Progress and Done statuses mapped to the respective columns.
• Sprint 1: Add 3 issues to Sprint 1 with story points field populated.
• Start the Sprint, move one issue to Done status and another to In Progress status.
• Complete Sprint 1 and choose to move the incomplete issues to New sprint(Sprint 2).
• Check the Sprint report, confirm the issue in In Progress status is listed under the Issues Not Completed section. 
• Start Sprint 2, map In Progress status to the Done column.
• Check the Burndown chart for Sprint 2 and note that the issue in the In progress status shows up with 0 Story points. 

Refer to the screen recording for details:

 Steps to reproduce the issue.mp4

原因

The reports honour the Board settings(column, filter) as well as the issue history in real time. According to the current Board settings(In Progress mapped to the Done column), issues in the In Progress status should be considered complete. This is why these issues appear in the Completed Issues list in the previous Sprint Report. However, the issue history indicates that these issues were moved to the next sprint. As a result, the Burndown chart includes these issues but assigns them 0 story points since they were completed in the previous sprint (as their status is mapped to the rightmost column).

結論

Board column configuration changes causes discrepancy in the Reports. The reports reflect the Board settings and the issue history in real-time.