-
Suggestion
-
Resolution: Timed out
-
None
Current Behavior
It requires at least 3 sprints in the current release to show a Forecast
Expected Behavior
It's possible that the previous release has similar velocity with the current one. As a user, I'd like the sprints from the previous release to be considered in the current one to show the Forecast.
Forecast in Release Burndown should be based on the sprints from the previous release
-
Suggestion
-
Resolution: Timed out
-
None
Current Behavior
It requires at least 3 sprints in the current release to show a Forecast
Expected Behavior
It's possible that the previous release has similar velocity with the current one. As a user, I'd like the sprints from the previous release to be considered in the current one to show the Forecast.