Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11945

Need admin controls for Atlassian teams

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 4
    • 11

    • 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 reference to this feature:

      [Create and manage an Atlassian team | Atlassian Support|https://support.atlassian.com/atlassian-account/docs/start-an-atlassian-team/]

       

      I recently created an Atlassian "team".  Afterwards, I noticed that the team is "open" by default and there is no way to change this setting.  This seems to be a significant oversight.  Teams should be able to be made private and controllable by the team owner so that the team can only be joined by invitation or by the owner adding a new member.  There are plenty of scenarios where you wouldn't want anyone in the org to be able to join a specific team.  

       

      I also see that there is no way as an org admin to see these teams.  This is also a significant oversight.  As an org admin, I should be able to see, edit, assign owners and members, and even delete teams in our org.  There should also be an org level setting to control if the org wants to allow users to be able to create teams.  Without this kind of oversight users can and will eventually create a large number of teams which will eventually be ignored or left orphaned which will add significant clutter in the long run.

       

      Please update Atlassian teams to be able to address the concerns listed above.  

       

      There have been a number of questions and comments on this asking for this functionality:

      How do i make teams private? (atlassian.com)

      Solved: How do I make a team private/closed? (atlassian.com)

      How do I change a team to NOT be open (atlassian.com)

       

      More context from similar requests: 

      #########################################

      Summary

      Only a current team member can remove a member. 

      How to reproduce

      1. Access "People" >> "Search people and teams".
      2. Find a group that you won't be a member of.
      3. Even a site-admin won't be able to remove a team member.

      Improvement suggested

      Site-admin should be able to remove a team member, or at least we should grant permission to a group to edit groups.

       

      #########################################

            [CLOUD-11945] Need admin controls for Atlassian teams

            SET Analytics Bot made changes -
            Support reference count Original: 10 New: 11
            Alex Stegani made changes -
            Link New: This issue is duplicated by JRACLOUD-80568 [ JRACLOUD-80568 ]

            Karri Adkins added a comment - - edited

            Now that it appears Teams is also connected to the newly migrated Opsgenie, we have no ability to manage/update/edit the Teams.  Too much rogue functionality creating a wild west scenario.  It is getting near impossible to mange or Admin Jira with this type of functionality.  This is my number one hated field in Jira.  I removed it from most of the projects were I could. 

            Then, again, I just came across a use case that kinda made me a bit surprised, I kinda liked telling them if they want it to work the way they expect, they need to manage the team membership accordingly.  Kinda felt good.  

            But I still don't like not being able to access it in case a Jira Admin is needed.

            Karri Adkins added a comment - - edited Now that it appears Teams is also connected to the newly migrated Opsgenie, we have no ability to manage/update/edit the Teams.  Too much rogue functionality creating a wild west scenario.  It is getting near impossible to mange or Admin Jira with this type of functionality.  This is my number one hated field in Jira.  I removed it from most of the projects were I could.  Then, again, I just came across a use case that kinda made me a bit surprised, I kinda liked telling them if they want it to work the way they expect, they need to manage the team membership accordingly.  Kinda felt good.   But I still don't like not being able to access it in case a Jira Admin is needed.
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 10
            Aimee Smith made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 948299 ]
            Bhavya Nag made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 935765 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Bhavya Nag made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 932010 ]
            Bhavya Nag made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 932010 ]
            Bhavya Nag made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 930895 ]

              4b7910ae10b4 April Chi
              7627d68c7dfd Phil M
              Votes:
              56 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated: