Issue Summary

A class responsible for various capacity calculations (DefaultTimeResourceTransformer) does not handle Kanban iterations properly.

That class uses the week's number to refer to iterations, ignoring the year. This means that e.g. the last week of 2023 will be treated as iteration 52, and the first week of year 2024 will be iteration 1. The code then assumes that "iteration 1" happened in the past (because 52 is bigger than 1) and removes it from the input data before performing its calculations.

As a result, many Kanban-based capacity calculations only work until the end of the current calendar year. The effect is more pronounced the closer we are to the end of the calendar year - in the last week of the year, calculations for only a single week will be performed.

This is reproducible on Data Center: yes

Steps to Reproduce

Use a Kanban board as an issue source for a Plan

Expected Results

The results on end-users are not clear, but it's likely that functionalities like auto-scheduling are affected

Actual Results

The results on end-users are not clear, but it's likely that functionalities like auto-scheduling are affected

Workaround

Currently, there is no known workaround for this behavior for Kanban-based boards.

The bug does not impact Scrum-based boards.