As Jira and Confluence Business Owner and Product Portfolio Lead, I want to be able to limit of users to create their own teams in Jira and Confluence Cloud to only Jira and Confluence System Admins to ensure the team structure remains clean and follows the organisation’s team structure to enable ease of assignment work to the correct team, clear naming/ identification of teams and that the structure of teams follows the organisations set up of Solution and Agile Release Trains. Unlike, now on Jira and Confluence Cloud, where anyone can create a team, which will mean the system has no naming convention, people in multiple teams, no ability to use this functionality to flow work to the correct team or track work by team in corporate reporting,  as it will be hard to identify which part of the organisation the team belongs to or control the set up and naming it will quickly become ungovernable and chaotic.

When does Atlassian start to realize that they can't simply add functionality to their applications without attaching any permissions to that new functionality? 🤔

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!

Hello,

Please, do we have any news on this matter? We need a permission that allows us to mention which groups can manage (create and delete) teams.

Thanks.

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.