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

      Atlassian Status as of 25 August 2020

      Unfortunately, in light of more urgent priorities, our team is not working on this feature anymore. We know this will disappoint many of you and is not the answer many of you were looking for. We’ll let you know when we are ready to begin work on it.

      Problem Definition

      Currently, the default access for team-managed Jira Work Management project is set to open and would allow anyone to access the project.

      This Open default is also hidden behind a dropdown, making it easy to miss:

      Suggested Solution

      Allow configuring default access to allow project owner to set the default access to Private.

      Why this is important

      If the project owner forgets and does not change the permission, restricted information could be leaked to users who should not have access.

        1. screenshot-1.png
          screenshot-1.png
          259 kB
        2. screenshot-2.png
          screenshot-2.png
          241 kB
        3. Screenshot 2022-06-15 at 2.37.54 PM.png
          Screenshot 2022-06-15 at 2.37.54 PM.png
          101 kB
        4. screenshot-3.png
          screenshot-3.png
          316 kB

            [JWMCLOUD-737] Allow configuring default access for team-managed projects

            Hope Man added a comment -

            80ad0544df9f 

            I tried to describe it to somebody else a while back here: https://community.atlassian.com/t5/Jira-questions/Re-How-to-limit-creation-of-quot-Team-managed-quot-projects-to-P/qaq-p/2603462/comment-id/919978#M919978

            But honestly, the easiest thing to do would be to just always send the email when a project was created telling them to check the permissions and warning them that the contents might otherwise be visible to everybody with site access.

            Hope Man added a comment - 80ad0544df9f   I tried to describe it to somebody else a while back here: https://community.atlassian.com/t5/Jira-questions/Re-How-to-limit-creation-of-quot-Team-managed-quot-projects-to-P/qaq-p/2603462/comment-id/919978#M919978 But honestly, the easiest thing to do would be to just always send the email when a project was created telling them to check the permissions and warning them that the contents might otherwise be visible to everybody with site access.

            Hi Hope Man, how can this be done?
            Are you using a "smart values condition"? If yes, which one? How to trigger for open project access?

            Thanks!

            Marco Schubert added a comment - Hi Hope Man, how can this be done? Are you using a " smart values condition"? If yes, which one? How to trigger for open project access? Thanks!

            Hope Man added a comment -

            If only there was a way to change it via automation, then one could build a rule that sets all newly created open team-managed projects to private.

            The only thing that I could do is create an automation that sends a warning email about this to users that created an open team-managed project and even that feels rather hacky.

            Give us SOMETHING, Atlassian.

            Hope Man added a comment - If only there was a way to change it via automation, then one could build a rule that sets all newly created open team-managed projects to private. The only thing that I could do is create an automation that sends a warning email about this to users that created an open team-managed project and even that feels rather hacky. Give us SOMETHING, Atlassian.

            Gigi Wong added a comment -

            We need this feature to have a control on data protection, preventing user wrongly create a project with public access instead of private one. Please consider to enhance on this feature. Thanks

            Gigi Wong added a comment - We need this feature to have a control on data protection, preventing user wrongly create a project with public access instead of private one. Please consider to enhance on this feature. Thanks

            23ef3e30d63c If you change the definition of this issue, then https://jira.atlassian.com/browse/JSWCLOUD-18478 can no longer be a duplicate. That issue asks for an admin control. As an admin, we have no control to either SET the default OR restrict access levels. When you have multiple clients in your instance, the only reasonable default is Private.

            Lenard Fudala added a comment - 23ef3e30d63c If you change the definition of this issue, then https://jira.atlassian.com/browse/JSWCLOUD-18478 can no longer be a duplicate. That issue asks for an admin control. As an admin, we have no control to either SET the default OR restrict access levels. When you have multiple clients in your instance, the only reasonable default is Private.

            Logan Cai added a comment -

            We need this feature to make sure new projects are only accessible to users that should have access to it.

            Logan Cai added a comment - We need this feature to make sure new projects are only accessible to users that should have access to it.

            Doug Nichy added a comment -

            Good move 23ef3e30d63c I see the same.
            Now I am noticing, when opening via WM, I do see the choose choice appear then quickly it flashes to open in the picklist.

            Almost like this is additional code on the page telling it to do that.
            So maybe Atlassian can just remove that auto choice of the picklist and the choose option is already there.

             

            Were so close 6 years in the making!

            Doug Nichy added a comment - Good move 23ef3e30d63c I see the same. Now I am noticing, when opening via WM, I do see the choose choice appear then quickly it flashes to open in the picklist. Almost like this is additional code on the page telling it to do that. So maybe Atlassian can just remove that auto choice of the picklist and the choose option is already there.   Were so close 6 years in the making!

            When creating a team-managed Jira Software project in the UI, the Access dropdown no longer defaults to Open:

            From my testing, the default to Open only occurs if you are creating a team-managed Jira Work Management project:

            This Open default is also hidden behind a dropdown, making it easy to miss.

            I am moving this ticket to the Jira Work Management project.

            Anusha Rutnam added a comment - When creating a team-managed Jira Software project in the UI, the Access dropdown no longer defaults to Open: From my testing, the default to Open only occurs if you are creating a team-managed Jira Work Management project: This Open default is also hidden behind a dropdown, making it easy to miss. I am moving this ticket to the Jira Work Management project.

            hr_suzuki added a comment -

            Without this feature, each time a new user is added, the permissions of each project must be checked

            hr_suzuki added a comment - Without this feature, each time a new user is added, the permissions of each project must be checked

            Doug Nichy added a comment - - edited

            Maybe this screenshot was glanced over.
            This guy has a "Choose an access level" picklist value.
            This guy also works at Atlassian now? Im a stalker and I might message them.

             

            Delfino Rosales!!! Where you at!

            Doug Nichy added a comment - - edited Maybe this screenshot was glanced over. This guy has a "Choose an access level" picklist value. This guy also works at Atlassian now? Im a stalker and I might message them.   Delfino Rosales!!! Where you at!

              Unassigned Unassigned
              nmohdkhalid Nabil
              Votes:
              353 Vote for this issue
              Watchers:
              185 Start watching this issue

                Created:
                Updated: