Great to see this was resolved for 2.2.4! Is there any timetable on the next JIRA Portfolio / Cloud release? The last update I could find was March 29th, but I couldn't see when the next release would be that would include this fix. (reference: https://confluence.atlassian.com/cloud/what-s-new-686863216.html#What'sNew-portfolio)

Thanks for the help! 

edit: I just noticed the linked cloud ticket that is in progress. I will follow that for updates. Thanks! - https://jira.atlassian.com/browse/JPOCLOUD-1740

Hey all,

This has been fixed for Server in 2.2.4.You can download the latest version here:
https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-jira/versions
Please let us know if you still have problems after updating.

We're also working on implementing the fix for cloud so if that relates to you keep an eye out for an update to this ticket.

Thanks,
Rhys | Product Management, Portfolio for JIRA

Also does someone know which issue is actually being worked on?  Is it this issue or is it: https://jira.atlassian.com/browse/JPO-1540

Glad to see the priority has been elevated for this bug.  Royal Caribbean is seriously re-considering this add-on precisely because of this problem.  This has been a problem since the beginning of December of last year and we are getting ready to close out Q1 with no workaround and no ETA.  I understand bugs are problematic, but can we at least get an estimate?  Otherwise we'll be looking at Big Picture or another plugin to spend our allocated budget on

We really want to use this field but this issue is causing a ton of problems for my teams who have historically used a custom field for Team assignment as opposed to this great new "Team" field. PLEASE help us by fixing this. 

To complement Rik de Valk's workaround, since by default Portfolio doesn't set the Team on Epics they won't be visible on the Agile board.

A fully functional "Team board" filter should look like this:
Team = 24 OR issueFunction in parentsOf("Team = 24") OR issueFunction in subtasksOf("Team = 24")

This is a very basic use case for any project involving multiple scrum teams (which is one of the main selling points of Portfolio): use JIRA Portfolio to plan and JIRA Software to execute.

Looks like to achieve that you have no choice but to buy (and master...) ScriptRunner. That brings the true price of Portfolio to 33% more than what's advertised (for 500 users).

We've made a complete new screen setup and we can't start using it untill this bug is solved. We need to have a required team field for dividing the work over multiple teams/boards. We really want to use portfolio on a high level in our planning but this is holding us back to fully use it at the moment.

If you happen to have ScriptRunner installed this offers you a work around for the Sub-Task issue with Team filters: you can set your Board filter as such:

Team = 24 OR issueFunction in subtasksOf("Team = 24")

This will complete your Board with all the underlying subtasks. 

By the way:I think Atlassian should fix all the JQL / Filter issues related to Portfolio in one go. Limitation in filtering on Parent Link and Team is a huge issue. Not being able to use operators such as 'in' and 'is not empty' is very constraining. 

We wanted to use the team field so we can create a scrum board per team and use this field for the JQL to get the issues to work on. That way we do not rely on any additional labels or updating of the queries and do not have to see the entire backlog (which is huge) for every team.

This is really crazy. A customer of mine wants to migrate 3,400 developers, analysts, and project managers to Portfolio and JIRA. The one workaround I've been given is to manually label issues to pull them via JQL. Which is ridiculous. For the size and scale I am operating at, this tool is un-usable for this without using other plugins to 'fix' it.
Low priority just makes me sad, I'm not sure how the heck to sell this with something seemingly so basic totally breaking my implementation. My implementation being the advertised implementation.