We are using Portfolio Releases (Cross-Project Releases) to group changes delivered by multiple teams into a single planned release/deployment. Most of the Projects are already there under our Portfolio Plan, but some projects are not (I'm assuming they might have been created by copying an existing project which was created before we implemented Portfolio).
Is there a way to associate an existing Project with a Portfolio Plan, or must this be done when the Project is first created?