We're implementing Portfolio at a pretty large scale. We have team members who create epics and stories in JIRA (on an Agile board, for instance) and need to set the parent link. In Version 1.0 of Portfolio, there was a permission called 'Portfolio for JIRA Restricted user' which allowed anyone with that permission to edit parent-links at any level of the hierarchy. Is there any permissioning that could work for our use case?
Add Editors to Plan: Have all users who need to edit Portfolio fields (Team, Parent-link, etc.) as Portfolio for JIRA Users. On a plan, add editors. Anyone who has Portfolio for JIRA User permission but cannot edit the plan can edit these fields. Problem with this solution: Anyone who has Portfolio for JIRA User permission can now create a portfolio plan. We don't want that.
You're correct - this is a gap in 2.x permissions. You must have Portfolio for JIRA User permission to edit Teams, Parent Link (from either plan or ticket field).
The workaround to add individuals as editors on a per-plan basis is probably 80% effective and manages your main pain point - allowing team members to add Parent Link from the ticket instead of the plan. But you're correct, they could then create new plans.
I think you'll have to live with this and address via plan audits weekly. You could also look at some custom CSS to hide the "Create Plan" in the Portfolio drop down and make that only visible to admins somehow, then funnel new requests into a queue.
Denver AUG Leader
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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!
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