Any update on this priority!   Under consideration in November, 2024.   We need functionality to turn off the create of a Team.  It is causing reporting issues and creation of Products and Product Families.

Hey, this is causing problems for us, with people duplicating or creating teams 3 times for the same purpose. This causes a problem on the visualisation and reporting side and we cannot prevent it, because everytime we sync and align, after some months, happens again.

We need a proper way to restrict who can create a team, edit name and members, delete.

Thanks.

.

+1 please ... this would be really helpful!

This is way too much rogue functionality.  We shouldn't be allowing users to do anything they want in Jira.  As it is it is impossible to ensure we can get teams following specific methodolgy b/c Jira is so wild west.  It is getting to the point being an Admin is useless.  

We need this fixed or implemented.  This is an issue for us as the team field integrates with other applications like Planview, our internal tool to show Product Team and Product Family views.   We had it turned off with data center.   Is there a work around or something on the administration side to not permit teams to update.  Causing a governance issue with multiple tools and syncing.

We just went live with Atlassian Cloud and functionality should have an OFF button!!!  

It's good to see at least this is on the roadmap as 2bda76795226 comment. But it would be even better if we could have this solution in place quickly. As I can imagine people create new teams and we all got flood when trying to find the correct team in Jira and/or plan in Jira. This would be nightmare for anyone trying to make a plan or manage a plan. 

https://getsupport.atlassian.com/browse/CHAT-59320

ETA please 4b7910ae10b4 

Giving the option to create teams by default to all users without any option to restrict it is a nightmare for admins!
You can tell the users as often as you want to not do it. They will! And it will create chaos and unnecessary work for admins to keept it under control.
You have a lot of options and permissions in Atlassian, so I can't understand why you provide such a feature without any option to restrict it? You should know it better already at the beginning.
Moreover this issue exists already over 4 years? Can't be a rocket science to add a permission to allow admins to disable "create teams" for users, isn't it?

Add my vote as well.

My thoughts (as I discussed during an interview with April a few months ago) are Teams should be on the same level as Users & Groups.  Being under org admin control.   Or at least have Permission entry like Sprint Managers where site admins can control this access.   Not use create Teams but also rename and delete.

Agree with the below and what everyone else has expressed.  Continuing to allow the "loophole" of all users to create a team and assign work to this team creates a domino effect of problems.  I'm happy to speak with the Atlassian product team (again - I spoke with Bhavya and others in July) to provide further background and try to influence prioritization of this.  This is a big deal to us and we are a fairly large (10k+ user) customer.

Thank you for the updates, April, but this will not address the primary pain point that all of us customers have been saying here.  Adding in a feature to "officially" manage teams is great, but if we keep allowing all users to create Teams, we're still allowing mess, clutter, confusion.  We as admins, should be able to fully disable Team creation by standard end users.

Hey 2bda76795226 ,

Thanks for the response! I'm in the midst of getting that roadmap item updated to reflect the feature better.

We'll be rolling out Managed Teams, which are Atlassian Teams can be connected to Groups. This allows for enhanced control in the creation and management of these Teams where Groups are the source of truth. As a part of this, you will be able to connect to Groups that are:

• SCIM-synced to an external source (SCIM-synced Teams)
• local Groups (non-SCIM-synced Teams)

If you're interested, we have an Early Access Program (EAP) open for SCIM-synced Teams open to customers. You can read more about the EAP and it's eligibility requirements here.

This doesn't stop the creation of Teams per se but with Managed Teams, end users can't create, delete, or manage Teams as the source of truth is the Group that i's connected to.

Let me know if this helps and if you have any further questions.

Regards,

April

Hey 4b7910ae10b4 !

I posted earlier regarding the "Admin-Managed Teams" item that is in your roadmap for "future"

Admins will have enhanced control over the creation and management of Atlassian Teams that have been ‘verified’ by them.

Is this the same thing here or something different? It would seem strange to communicate something on a roadmap that is only "under consideration"?

Cheers

Hi all,

I'm April, a product manager on Atlassian Teams 👋.

I appreciate you sharing your insights and use cases regarding this topic around preventing the creation of Teams. This has been a high demand feature request. We acknowledge your pain points and recognise the importance of this. Our plan is to hopefully explore this further in the upcoming year. 

We've conducted research and have some early thoughts and explorations.

I'm keeping this as 'under consideration' because:

• It's not on our official roadmap yet (so timelines TBD)
• It's too early to tell what the solution would look like
• But it is something that is on our radar

Feel free to reach out in the comments if you have any questions or comments around Atlassian Teams. 

Best regards,

April

Is this planned to be resolve via https://www.atlassian.com/wac/roadmap/cloud/admin-managed-teams?status=comingSoon;future&p=446799e7-d6 ???

4b7910ae10b4, can you give me an update?

+1 Makes Teams almost unusable if not manageable on a company basis.

We are right now moving to Atlassian Cloud and luckily I found this suggestion and comments here. We will now cancel our plans regarding using Teams functionality and guide people against using it. It's a critical requirement for us that Teams are centrally managed and no one in our organization is able to suddenly create parallel or duplicate teams. Before this is available, Teams functionality would certainly just produce noise into our system.

Please add this functionality.  New features for the most part should be able to be toggled on or off.  I feel like sometimes Atlassian doesn't think through the impact these changes have to larger enterprise type clients.  I now have 25k users creating random teams.  Same thing with Goals, Atlas, etc.  Seems it's forced to us where larger changes like these for large companies need to have a plan in place and guidelines, guardrails, etc.  Else the users will go wild with what they do.  

Please add this ability as soon as possible. We are unable to continue using Teams as an identification mechanism for our Jira teams, as there are too many duplicate teams, with no way of controlling which team works on which piece of work. 

This is breaking your clients' critical systems by introducing chaos, Atlassian please assist urgently and fix this.

Please add ability to set permissions on who can create teams.  This should be so easy to do and yet is still not done.  We already have data integrity issues with people creating teams, duplicate names, duplicate teams, people who don't understand what they are used for.  Very very difficult to maintain and run down which ones should be deleted.  BASIC FUNCTIONALITY that is a necessity especially if you are integrating the concept of Teams into so many features.

4b7910ae10b4 hi can you please provide an update?

We need Global permissions to avoid "create Team" by regular users and restrict it only for admins. this feature conflicting with our Org chart and ldap groups. This kind of Global permission or other way to limit this feature is very very necessary for our organization.

Please prioritize this, along with JRACLOUD-81740 (Ability to limit who is able to create a new team and who is able to delete any team).  We're using Teams as part of our official hierarchy, and eventually the data in Jira will be used to drive accounting.  Not having the ability to properly administer Teams creates a host of problems and introduces so much waste in the system.

We are using teams to communicate who is working on which subject within or work environment. As we have a lot externals invited it is more than inconvenient not to be able who can create and edit the team. It is crucial for us to have control over team administration.

Please add the Team Creation restriction.  Since Atlassian rolled out this I have had 50 extra "new" teams created on the fly and are being used inadvertently by team members.  This is causing a lot more trouble than its worth.  I would like to control who is able to create a team that is used throughout Jira.  We have management reports incorrectly reporting team activity due to this feature. 

We need this pease.  With Teams now available across Atlassian ecosystem, this has created a lot of mess!  All users should not be able to create teams.

+1

Moving this from gathering interest to under consideration. We've heard a lot feedback about this, and we're exploring options for how we might implement additional controls for team management.

We created hundreds of Advanced Roadmaps Teams to help distribute work over thousands of users. We have a strict naming convention so that they can be quickly found in the Team field.

Previously we had confusion with the prominence of "Atlassian Teams" in the UI and users randomly creating teams and not understanding the difference between Advanced Roadmaps and Atlassian Teams. Now with the unified team paradigm we have duplicates for about 1/3 of the software teams, teams that came from Confluence and don't represent software development,  and no way to monitor new team creates or even get a full list of the existing teams. And users can freely rename, which breaks our integrations.

The new Teams functionality gives us two significant problems, making it pretty much unusable...

1. Any team member can DELETE the Team.  This could be hugely costly - if the Team is deleted after we carefully set the Team fields on 100's or 1000's of Issues, there is no way to recover that lost data.  Team deletion needs to be restricted to a trusted few.
2. Any Jira user can CREATE a Team.  We want to operate a carefully maintained set of Teams (approx 10), so that Issues can be assigned to the correct department.  If all Jira users can freely create additional Teams, then surely they will, and that will pollute our carefully maintained set of Teams.

Please prioritise.  Many thanks.

new Global permission "Create Team"  [2] pleaseeee

new Global permission "Create Team"  

This is a huge problem! Fix this ASAP! 

My organization has depended on legacy Teams as introduced through Portfolio/Advanced Roadmaps many years ago.

While I appreciate this attempt to make them more broadly usable in the Jira family, Atlassian has removed my ability to effectively manage them.

Perhaps Atlassian thought that Teams were not leveraged very much and felt free to enable everyone to create them freely ?

PLEASE give me back the ability to closely manage my instance and how my organization chooses to expose features to its members.

Feel free to contact me directly for any further information.

We want to use "Teams" to assign issues to our different teams in Jira Service Management, but if all agents can create their own teams the list will include a lot of wrong teams. 

We want to be able to limit Teams creation to only administrators, that way we can control which teams will be in the list of the field "Teams" and can create a filter for each team based on that field. It will be total mayhem if all 300 agents can create their own teams, we only want our 15 official IT teams in the list.

Can't we just have a product role Guests as we do have for Confluence, please?! Why just implementing it for one application?

Many users in our company are creating their own teams, but we already have a tool to control resource capacity, that is connected to Jira, where regular teams and functional teams are established and managed. The problem is that each time a new one is created into Jira by a user, it pollutes my data.

Some users created a team with only themselves just to test it.

My company is managing teams by create team function. 

Actually, many user create team and we can't manage teams in my company. So we want to restriction user on my company who can create or edit teams. We can assign permission to a fews user in my company.

Thanks!

Dear Customers,

With the release of the Team field in Jira and migration of Advanced roadmaps shared teams to Atlassian teams, we have seen renewed interest in the ability to disable/limit creation or access to teams altogether.

For Advanced roadmaps customers:

• the integration of Advanced roadmaps teams, Atlassian teams will not automatically populate advanced roadmap shared teams with the rest of the Atlassian teams. Advanced roadmaps teams are managed separately in the advanced roadmaps Teams tab.

For the rest of the customers:

• Please help us understand why would you like to have the teams functionality disabled. We are currently investigating how the new team functionality is impacting our customers and what particular concerns would be addressed by disabling teams.

Thank you

Creating a major blocker to offer Confluence Cloud services to our Clients , since they can see the names and email addresses of other clients via this Team functionality in Confluence.

Though the teams in Jira works fine in terms of maintaining client confidentiality.

Search people and teams + the user profile in Confluence is blocking us and we are forced to use on-prem data center instances due to this.

This lack of ability to permission has the potential to cause a data breach in my organization, a serious consideration for us as we grow and scale into Jira working with external customers. this is simply unacceptable and needs to be addressed.

This issue severely limits the possibility of including customers in projects, as customers shall not be able to see any users other than those involved in their projects. Without subscribing to a Jira premium plan, the "Team" feature is practically useless, but creates a loophole, allowing every user to see any other throughout the whole Jira instance.

Only possibility to avoid this is to deny the global "browse user" permission to customers, which in turn disables @mentions and some good search possibilities.

Atlassian has long started rolling out new features without prior consulting with users. Most of the functions are ill-conceived and hence serious holes come out. If Atlassian continues to ignore users' opinions, nothing will change