-
Type:
Bug
-
Resolution: Obsolete
-
Priority:
Low
-
None
-
Affects Version/s: 2.2.2
-
Component/s: Scheduling
-
5
-
Severity 3 - Minor
-
29
NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.
Problem Summary
When new sprints are forecasted by Portfolio, it uses the count of sprints on the plan as basis for the sprint numbering, not the total count or the number of the latest sprint.
Expected Behavior
Use the same engine as Agile does when forecasting sprints, where it gets the number of the latest sprint.
Actual Behavior
Because of this, it doesn't matter if I had 30 sprints completed in the past, if I only have 3 active or future sprints, JPO will start counting on Sprint 4.
Steps to Reproduce
- Create a Scrum Board;
- Create 2 sprints;
- Complete 1 sprint;
- Create a Portfolio plan and connect to the board;
- Forecasted sprints will start on Sprint 2;
Workaround
No workaround available at this time.
- relates to
-
JRACLOUD-88069 Consider number of already completed sprints for teams connected to board issue sources
- Closed
