We are also impacted, this needs fixing.

Example: user raises support ticket to us about slow portfolio plan. We can't open the plan because it is restricted because this Jira or the content on the plan is not meant to be visible to all users on Jira(say different customers of same company using the instance). Therefore we have to 

  a) guide/ask users how to add support person account, adding extra delays and work for our team and the reporter

  b) use scriptRunner built in feature and become the user first, adding extra delays and work for our team

in order to add the group that is already mentioned in Portfolio Permissions to be able to work and collaborate on solving the issue reported.

Now either this group should be automatically added when it is switched to ""private"" with explanation why, or it should be built into the Portfolio that they are part of ""Editors"" if the plan is ""private"" even when not specifically named.

Please note that users can't add groups they are not members of, ie: jira-administrators / jira-system-administrators.

Now given how Jira software and Jira service desk works, and the fact that Portfolio permissions separate configuration page is present, it begs the question what is it there for, if it clearly does not work as expected compared to mentioned Atlassian tools as examples.

I do not understand such ignorance given that the issue is still present in v 3.1 and this bug is here for ages !

+1

This is a problem for SOX/SOC2/PCI audit and compliance.  We cannot go re-activating users without raising flags with auditors.  This needs to be addressed!  

Michael: valid point about Script Runner (which honestly should be bundled into JIRA given that they force you to use it for many basic features)

I do agree about changing ownership, which is also an auditable change. I fully support them working the same as private filters and dashboards, which are not casually viewable but can be adjusted as you mention.

@Jo Rhett, you can only 'become' a JIRA user if you have yet another plugin installed (i.e. scriptrunner) so I do not see that as a valid option.

I still do not understand the issue with this suggestion, could Atlassian not make it just like with Dashboards and Filters so the the JIRA Administrator can change the owner when required. Otherwise a lot of plans will remain forever when an owner of a private plan leaves the company right? Cleaning up JIRA is already such a hard task for admins.

Please make this optional. PMOs routinely have to work on Plans that may not come to be, and which involve work done by JIRA Admins as individual contributors. Speaking as a JIRA Admin, I don't want people coming to me asking to see a plan that a PMO isn't ready to share yet.

If it is truly necessary JIRA Admins can always "become" a user. It provides the necessary backup, but it's also an auditable event so it won't be abused.

Agreed! After 1,5 year this "feature" is still not in Portfolio. Very important for the administrators of the tooling.

.

Agree!

Portfolio Administrators should ALWAYS be able to change plan permissions.

Agreed. JIRA Admin should able to access to all plans including private plans.