Issue Summary

Historical sprint-related reports become inaccurate if the statuses are no longer mapped to board columns. When a workflow change occurs and statuses are changed, users are (unfortunately) encouraged to remove statuses that no longer exist in the current workflow by the UI prompts. If the user does this, it will break historic reports.

Steps to Reproduce

1. Get a completed Sprint where the Velocity Chart has a commitment and completed data;
2. Edit the project workflow to use only different statuses and map them on the board.
3. Check the Velocity Chart.

**Similar impact can be seen also on the Sprint report.

Expected Results

The commitment and completion will change.

Actual Results

The report should keep historical information.

Workaround

As a workaround, in the new workflow, we must ensure that all the previous statuses are included but without transitions to them. This will allow the report to use the status data for historical purposes while preventing users from accidentally transitioning issues to unused status.