+1, this is a very important feature for us as well. I spending more time finding hacks instead of having this functionality built in, the implementation shouldn't be that hard as this behavior exists already.

Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

Also critical for us!

Without this, we have to use a separate custom field, which is clunky and not helpful.

I'm also interested. Currently I want to add one team (ie. more than 1 person). Thanks.

Is this feature coming soon? We need to be able to assign an epic to multiple teams. 

We have multiple Epics going across team and need to be able to plan accordingly. We NEED to be able to assign more than 1 team to an EPIC.

Need this feature because the higher you go up the Jira Portfolio issue hierarchy, the more likely that an issue's children will be assigned to various teams.  It is not uncommon for a single Epic to have child stories spread across multiple teams.  For Initiatives, it even more likely that its child Epics belong to multiple teams.

Leaving the Team field empty is not a suitable work-around.  Although scrum board filters and Portfolio plan issue source filters can account for Team = XXXX OR Team is EMPTY, there are difficulties in Jira Software (Server) 8.3.1 and Portfolio for Jira 3.8 whenever Team is empty:

• Portfolio's improved experience UI shows Initiatives without a Team value as "Unassigned", and these Initiatives cannot be expanded.
• Scrum boards in Jira may not show Epic Labels on Stories properly when the associated Epic lacks a Team value.

It may be a requirement of scrum that a story only be permitted to be assigned to a single team.  But there's no need to force that kind of restriction.  My suggestion: allow any number of teams to be assigned to any issue, and see where that leads.

We really need this issue fixed as soon as possible.

We are using Portfolio for Jira v2.18.0

We are facing this issue:

I have an EPIC, and I have 2 User Stories for that Epic.
I have 2 different teams assigned for the 2 different User Stories.

In Portfolio, it shows there are 2 teams assigned for the EPIC. ( It is calculated by the Portfolio plugin automatically)

We made Portfolio's Team custom field visible in JIRA also.
The problem is that when I open the Epic in JIRA, I can't see that 2 teams, only 1 or none of them.

This is really needed.

A must have.

Aside from all the other above comments, there is one more reason to be able to assign an epic to more than one portfolio team:

The portfolio team field is very useful to organize boards base on a JQL filter that responds to "Team =" However, the problem with organizing boards based on the portfolio team field is that the epic that are only assignable to one team will not be shown on the boards from other teams that are also working on that same epic/s. In order to do that you will have to create a system of labels, component or whatever other method so that these epics are also shown. This is killing the JQL simplicity behind the boards. Not only the JQL but also the amount of detail that has to be added to an epic, as in order for an epic to be shown in more than one team board the user will most likely have to add a label or component.

How much leaner and user friendly would the process of assigning epics and displaying work in boards if this feature was integrated?  a lot 

Need this feature!

This is almost a must-have feature

This is much needed in the SAFe implementation

+1 without this function it's impossible to create a plan that involves multiple teams without getting very detailed (e.g., breaking epics down into stories) – We use Portfolio to do high level planning to save us from breaking down epics until we're ready to work on them.

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.