Summary

In a chain of dependencies, a DONE issue breaks the scheduling of the remaining issues when being auto-scheduled.

Diagnosis

• There is a transitive chain of dependencies  ISSUE-A > ISSUE-B > ISSUE-C.
• The dependency setting is set to Sequential for the PLAN settings.
• ISSUE-B is in DONE status. Since it is in DONE status, ISSUE-C should be scheduled immediately after ISSUE-A.
• However, when we try to see the results after auto-scheduling, we see that ISSUE-C is not scheduled immediately after ISSUE-A.

Cause

As  ISSUE-B is in Done status, the scheduler considers that ISSUE-C can be scheduled as soon as possible.  ISSUE-A and ISSUE-C are assigned to different teams and therefore there is no reason they should be scheduled one after the other.

Solution

The solution here would be to add a  direct dependency between ISSUE-A and ISSUE-C.

However, if all the issues would have been assigned to the same team,  ISSUE-C would have been scheduled immediately after ISSUE-A.