How to assign multiple Portfolio Teams to a single user story in Portfolio?


With the new upgrade of Portfolio it seems that it is not possible to assign multiple Portfolio Teams to a single user story in Portfolio. 

This was not the case in previous version of Portfolio.

Need help in this regard.

Does JIRA recommends to use One Team for One Story?or any other reason?  Justification of the same  from the Atlassian Development team  would be great.


How to overcome the situation if i want the story to be assigned to multiple Portfolio Teams. 





2 answers

1 vote
Hey Ashwin,
You can only assign multiple teams to issues above the story level (i.e epic or higher). This is consistent with older versions of Portfolio where stories could only be assigned to one team.
A story is generally a work item carried out by a single team. If a story is large enough to require multiple teams then it’s likely an indication that it should be broken down into more granular work items. Perhaps the story is better represented as an epic or further broken down into separate stories? 
If you want to associate multiple teams on a single issue I recommend using an epic to represent the work. Break down the work into stories then assign those stories to different teams. The multiple teams will then be reflected on the epic.
Please let me know if you need further assistance.

How do you assign multiple teams to an epic? It seems to be a radio button for me. 

Hey Paul,

You're unable to assign multiple teams directly to the epic but you can assign multiple teams to its child stories which will then be represented on the Epic.



The problem with not being able to assign more than one portfolio team to a same epic is that, if I base my Scrum Boards filters on teams, then the boards will not show the epics that are not assigned to an specific team. 


If I break an epic into multiple stories that are then assigned to different teams, the teams that are not the main epic assignee will not have the epic shown on their board. That, kind of sucks. 


Any work around that is not an ugly JQL filter behind the board??

@Bernardowe used this condition in our JQLs:


OR issuetype = Epic AND Component = TeamComponentName


It requires tagging your Epics with a Component (or Label would also work) but then the Epic can be viewed in Agile Boards and Portfolio Plans for multiple teams. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

950 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you