Boards based on Portfolio Team (shared) field
Asked by Bernardo:

Hi,

I'm configuring boards with JQL filters that are based on shared portfolio teams. Here my problems:

\* When I create issues directly from the backlog this issues do not get automatically assigned to the portfolio team in which the board is based. Whereas if I instead use a custom team field to configure our boards the system will recognize it and when I create an issue directly from backlog it will automatically assign it to the specific custom team field I base the board on. Any workaround or tips in order to get the issues directly assigned to a shared team in which I base a board when I create this issue directly from the backlog (no scripts please)

\* Also, how is it possible that the "Team" field from portfolio can not be configured to to be displayed as part of the "Issue Detail View" within a board? This makes no sense. Is there anything I can do, any tips?

Thks and best regards,

Bernardo


Answers:
author: Earl McCutcheon
body: Hey there Bernardo,

The Portfolio Team Field does have a few limitations currently, and being added to the Issue Detail View on an agile board is currently one of those limitations.

We have the following Feature Request tracking this:

* <https://jira.atlassian.com/browse/JPOSERVER-1847>

Make sure to add your vote and any additional feedback you have to the feature request to [help in development and prioritization efforts](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html)on this one.

Regards,  
Earl


author: Shannon S
body: Hi Bernardo,

Without the possibility of use of scripts in [ScriptRunner](https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=server&tab=overview), this is no other way than the manual way you are currently using to get the association.

There's a feature request below that asks to display a warning when adding unassignable users to your team:

* [JPOSERVER-2364](https://jira.atlassian.com/browse/JPOSERVER-2364)

For your 2nd question, Team field is on the main issue view. If you don't currently have it there, perhaps it has been removed from that screen?

You can use the "Where's my Field" in Admin Helper to see for sure:

![Screen Shot 2018-07-05 at 9.57.34 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/26320i2F76689C864B754D/image-dimensions/567x222?v=v2 "Screen Shot 2018-07-05 at 9.57.34 AM.png")

Let me know if you have any questions!

Shannon

comments: author: Bernardo
body: Hi Shanon,

Thanks for your reply, in regards to the first question, ok, got that, scrip runner, however, from a UX perspective it would be if users could create issues directly from the board and assign this issues to the team without scripting. As this is possible with any other custom field I use. Example:

\* I create "Scrum Team" custom field based on a single choice drop down. I use some some basic JQL to configure a team board (project = XYZ and Scrum Team = ZYX) by using this filter, If a create and issue from the board, the system will automatically assing it the the "Scrum Team" = ZYX. In my opinion same logic should be applied when using and out of the box Portfolio Field "Team"

My second question:

I think you did miss understand it. I am not referring to the main issue view or screen, my field is in the screen 100%

I am talking about the "Issue Detail View" within a board. Without the possibility to manage that field on the Backlog view or Active sprint, the integration of portfolio into the boards kind of sucks (see below) any suggestion.

Thanks!

![issue detail view, scrum board.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/26561i2F7AB2F436370CE5/image-size/large?v=v2&px=999 "issue detail view, scrum board.PNG")


Tags: advanced-roadmaps