+1

Agree - you can have different teams associated to support a single epic and want only those items that are related to an epic to appear on their board, but with the same ability to narrow down by epic.  Consider larger projects or when teams swarm.  Not sure the reason or value for the initial restriction. 

We also want to keep it as one epic as progress towards the completion is important and don't want to cause confusion if we are forced to break it into team 1, team 2, team 3 to meet a tool's limitation vs what the business needs to track. 

We're running into this issue so that Advanced Roadmaps doesn't work too well for some of our use cases, specifically the big picture view where we want to look at the epics teams are actively working on but sometimes they might have a bug or a small story from another epic and we don't want that noise - we're on Jira cloud so I think this is the right issue.

Good one to do; people from different teams and boards should be able to contribute to a single Epic or even implement the same customer outcome on different technology. 

I would like this feature implemented as well. We are a big project group where an EPIC is assigned to multiple teams and Stories are assigned to a specific team. With JIRA portfoli not supporting this, it an issue. It will be great if you can look at prioritizing this.

my comment

+1
If u have different team and some initiatives it's really helpfull to have that kind of assignement, same as when u choose team member that can be assigned to that level

Please implement this feature as it is a very big roadblock for our implementation of the tool and to properly track the capacity and progress of various teams. We only include initiatives and epics in Portfolio (stories remain in JIRA), and our epics in many cases span multiple teams.