-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 2.2.2
-
Component/s: Scheduling
NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.
Summary
Scheduling algorithm considers Rank first than any other values such as dependencies. When there are multiple backlogs and teams working on the same Plan, it may get an unexpected result.
Steps to Reproduce
Have Backlog A and Backlog B runs in parallel on two different backlogs with assigned to two different teams.
Backlog A has the following backlog (rank in brackets):
BACKLOGA-1 (1)
BACKLOGA-2 (2)
BACKLOGA-3 (3)
BACKLOGA-4 (4)
BACKLOGA-5 (5)
Backlog B has the following backlog (rank in brackets)
BACKLOGB-1 (6)
BACKLOGB-2 (7)
BACKLOGB-3 (8)
BACKLOGB-4 (9)
BACKLOGB-5 (10)
If BACKLOGA-1 has a dependency on BACKLOGB-2 it does not schedule it straight after BACKLOGB-2 completes (which it should, because it is first in the backlog and has the highest rank).
Expected Results
BACKLOGA-1 scheduled right after BACKLOGB-2
Actual Results
BACKLOGA-1 scheduled after BACKLOGA-5
Notes
This is because, in scheduling, Rank is considered first then other values such as dependency. It is an expected behaviour, JPO-1531 open to adding this in the documentation.
- relates to
-
JRACLOUD-88677 Schedule Dependency equal to Rank on Multiple backlog
-
- Closed
-
-
JSWSERVER-24881 Auto-scheduling of dependencies based on date, not rank
- Gathering Interest
- mentioned in
-
Page Loading...