Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-18859

Ability to restrict who can "Browse Projects"

XMLWordPrintable

    • 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.

      In Classic projects, there is a "Browse Projects" permission. This makes it possible to give jira-users read access to one project, without allowing them to see all the other Jira projects.

      This is not possible with Next-Gen. If a jira-user has any permission in a Next-Gen project, they can automatically see the full Jira project list. This is an issue if the jira-users include clients, for example, who have privacy concerns.

            [JSWCLOUD-18859] Ability to restrict who can "Browse Projects"

            Matthew Hunter added a comment -
            Atlassian Update - April 3, 2022

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - April 3, 2022 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            Lu added a comment - - edited

            How I wish this was a High/Highest priority for you, guys.

            Let me briefly explain our company situation: 

            • We have a lot of (non-Next Gen, let's call them regular) projects in Jira 
            • When we learned about Next Gen, we thought it could be cool so we created some using it (and yay to roadmaps, but even YAYER to the fact they're coming to regular projects!)
            • Most of our projects are configured with special permissions so that clients can access their project's Jira and see current status, reports, and whatnot BUT
            • We realized that every client that has access to ANY project in our instance can see all other Next Gen projects we have. And that's not acceptable. Not even remotely. We don't even need them to know the names of other clients/projects, let alone browse with read access.
            • As part of the PMO, I recommended to stop the use of Next Gen projects, and that's why we are sticking to and only using regular Jira projects until this is fixed. 

             

            And I'm sure I'm not the only one that works in a company with these problems. 

             

            Thank you so much for your attention.

             

             

            Lu added a comment - - edited How I wish this was a High/Highest priority for you, guys. Let me briefly explain our company situation:  We have a lot of (non-Next Gen, let's call them regular) projects in Jira  When we learned about Next Gen, we thought it could be cool so we created some using it (and yay to roadmaps, but even YAYER to the fact they're coming to regular projects!) Most of our projects are configured with special permissions so that clients can access their project's Jira and see current status, reports, and whatnot BUT We realized that every client that has access to ANY project in our instance can see all other Next Gen projects we have. And that's not acceptable. Not even remotely. We don't even need them to know the names of other clients/projects, let alone browse with read access. As part of the PMO, I recommended to stop the use of Next Gen projects, and that's why we are sticking to and only using regular Jira projects until this is fixed.    And I'm sure I'm not the only one that works in a company with these problems.    Thank you so much for your attention.    

              Unassigned Unassigned
              iekeh Ijeoma Ekeh
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: