Relates to JPO-1532

Auto-scheduling of dependencies is done in such a way at the moment that it does not work for plans with more than one team/backlog who have dependencies between those backlogs. It only works reliably for dependencies within the same backlog.

This is because a blocked item will be assigned a virtual rank below the item that is blocking it, and does not take dates into account in any way. This means that for teams with independent backlogs (and with no knowledge of the rank of the other team's issues) dependency scheduling can be very strange indeed (see JPO-1532).

A workaround for this is to disable the auto-scheduling of dependencies, but this removes one the of the most attractive features of Portfolio for JIRA.
A much better way, and more intuitive way, of scheduling dependencies is to do so based on the predicted end date/final sprint of the blocking item.