We have a situation where the same team is split between multiple projects. Right now the only ways to represent the team in JPO are either splitting the team manually (which interferes with automatic scheduling) or creating a kitchen sink plan (which is a problem because of JPO-159 and is an antipattern in itself, since it becomes unwieldy).

It would be great if teams were a cross-plan entity and planning was a cross-plan activity, supporting use cases like this (when I say project I mean a waterfall-style activity):

1. If project X is the highest priority and project Y is the second-highest, can we go live with any other projects at the next release date? Schedule them and fill up the rest of the capacity with longer projects and our ongoing enhancements Scrum. JPO plans that the first architect will work on project X, then will move to project Z. The other architect will work on project X as well, then a few epics, then project Y, then more epics.
2. Oh no, project X task X.1.2 has slipped by two weeks! Reschedule everything, taking into account that task Y.2.4 cannot be shifted, since it is done by an external vendor. Now the architects don't have time to work on project Z, it slips into the next release, and architect 1 is scheduled to work on epics, while architect 2 moves to Y straight from X.