Can Portfolio manage across Projects and Teams?

[Jeffery Faneuff]

I am used to managing everything by Project which was a hard boundary for teams.  It seems like this should be possible via the corresponding project releases.  Can a team be assigned to an Initiative under one project and then to another initiative under a different project (after the first one is done)?  Can an epic under one project have a dependency on an epic in a different project?  In other words, do Project represent hard boundaries or are they used more like tags?    Thank you.  p.s.:  Yes, I watched all the Portfolio intro videos.  

https://www.atlassian.com/software/jira/portfolio/

Intro Webinar
https://www.youtube.com/watch?v=849rNIXYx74

Getting started 9 mini-videos
https://www.youtube.com/watch?v=M_BXgSw1RV0&list=PLaD4FvsFdarTthRrvRYXsYCYDeHooNKio

Long-term planning
https://www.youtube.com/watch?v=S5akHU5KvsI

[Martin Suntinger]

Hi Jeffrey, yes absolutely. Portfolio focuses on a combined backlog of issues pulled together from multiple JIRA projects. Teams are defined in Portfolio, and can be flexibly assigned to work originating from various JIRA projects. Dependencies can be between epics and stories across different projects. Projects are not a hard boundary, they are merely a source of issues on the shared backlog for Portfolio. 

The one place where some constraints come into play is around releases, resulting from the fact that in JIRA an issue can only be assigned with a release (fixVersion) in the same project. For this reason, Portfolio allows multi-linking of a release in Portfolio, multiple versions in JIRA (1 per JIRA project), to represent a cross-project release. For example, if you plan towards one shared release across 3 projects, you create 1 release in Portfolio representing it, but link it to the versions in the 3 projects in case you need to have this release also represented in your JIRA projects.