JIRA Portfolio team field on issue create

Question

Without explaining the extensive customization, I’m using JIRA and Portfolio cloud. I have the Portfolio “team” field surfaced as a custom field in JIRA and it appears on several issuetypes and in several projects. When creating a new issue as an admin in both products, the field behaves as a normal custom field. When creating a new issue as another user without admin, the field is present (help text visible), but the dropdown with Portfolio teams is not visible and users cannot interact with the field. Once the issue is created, the team field is editable and behaves as a normal custom field for all users.

Does anyone know what permission, in which product, drives this behavior? I experimented with no luck. My end goal is to allow non admins the ability to select a portfolio team on creation of a new issue.

Dave · Answer

Hi @Chris Covert,

It's not possible to update the Team for a sub-task because it's considered part of the issue (in a plan the sub-task will always inherit the Team value from it's parent issue). This is why you also can't have a different sprint for a sub-task, the sub-task considered to be part of the issue.

Regards,

Dave

Chris Covert_h0jutu · Answer

Having the same issue but with sub-tasks only.

Is this just a limitation of sub-tasks, they don't allow Advanced RoadMaps Team field to be updated?

Earl McCutcheon · Answer

Hi Nick,

Thanks for the screenshot and this occurs when the user is missing a global permission for portfolio granting them the ability to see the fields, the minimum being the "Portfolio for Jira Viewer" permission, which grants a user the ability to browse and view plans in read-only mode.

But in addition to viewing the plan in portfolio in read only, if you expose the portfolio field on a screen in Jira then the View permission is required to see the contents of the field but as the field is exposed to jira the user can create or edit an issue then the field will be able to be modified jira side.

When a Portfolio Field is  added to a screen in Jira, the user can update parent links, teams, and target dates of issues on the jira side where that user has permission to edit the issue.

Regards,
Earl