Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-88142

Allow sysadmin/admin to access private plans

XMLWordPrintable

    • 3
    • 13

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      Summary
      At the moment, sysadmins/admins cannot see a private plan unless they have been explicitly granted access. It would be desirable that admins have access to all plans.

      Use case
      This is to allow sysadmins/admins to see Private Plans for cleaning up purpose, for example when the said use has left the company.

          Form Name

            [JRACLOUD-88142] Allow sysadmin/admin to access private plans

            Ashok Karuppiah added a comment -

            4 years and counting

            Ashok Karuppiah added a comment - 4 years and counting

            Esther Lansbergen added a comment -

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

            Esther Lansbergen added a comment - Agreed! After 1,5 year this "feature" is still not in Portfolio. Very important for the administrators of the tooling.

            Gemma Haenen added a comment - - edited

            .

            Gemma Haenen added a comment - - edited .

            Gemma Haenen added a comment -

            Agree!

            Portfolio Administrators should ALWAYS be able to change plan permissions.

            Gemma Haenen added a comment - Agree! Portfolio Administrators should ALWAYS be able to change plan permissions.

            Jahir added a comment -

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

            Jahir added a comment - Agreed. JIRA Admin should able to access to all plans including private plans.

            Michiel Schuijer added a comment -

            +1

            Michiel Schuijer added a comment - +1

            Marilyn DeLuca added a comment -

            Yes, how are JIRA admins supposed to manage our environments when a Portfolio user can remove the jira administrator from the plan. This isn't advertised as working this way. Now I don't even know what or how many plans are in my environment. Why is there not a fix for this?

            Marilyn DeLuca added a comment - Yes, how are JIRA admins supposed to manage our environments when a Portfolio user can remove the jira administrator from the plan. This isn't advertised as working this way. Now I don't even know what or how many plans are in my environment. Why is there not a fix for this?

            Raghu S added a comment -

            +1

            Raghu S added a comment - +1

            Nirmit Patel added a comment -

            We also have similar case where System admins are also not able to view private plans and blocking our ability to grant access to users. In this case, we can not identify who is the project planner for that private plan. Do we have any option to find out the planners user ID?

            This also blocks our ability to evaluate portfolio to see how many total plans we have currently.

            Nirmit Patel added a comment - We also have similar case where System admins are also not able to view private plans and blocking our ability to grant access to users. In this case, we can not identify who is the project planner for that private plan. Do we have any option to find out the planners user ID? This also blocks our ability to evaluate portfolio to see how many total plans we have currently.

            Maree Milne added a comment -

            +1

            Maree Milne added a comment - +1

              Unassigned Unassigned
              akavelar Albert Kavelar
              Votes:
              42 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated: