🙌 Organization admins can now change or manage any team

[#1]

With the latest upgrade to Atlassian teams, organization admins can now make changes to any team profile used across most Atlassian cloud projects — even if they’re not a member. When viewing a profile for a team you’re not a part of, you’ll notice a few extra buttons in the left sidebar that let you:

• Change the header image
• Add or remove members
• Edit team name, description, and settings
• Add links to the profile
• Delete the team

Previously, an organization admin would have to join a team before they could make any changes to it and then remember to leave the team when they’re done. While it may seem like a small inconvenience, it really adds up when you have to repeat the process for a large number of teams at a time.

We hope this makes your life as an admin easier, and look forward to your feedback 🙂

[Nathan Allen]

Will we also be able to manage teams using an API? I’d love to sync this to our already existing people management tools

[Christine Absil]

Not clear to me at all
Is Atlassian team a plugin?
Is this about jira? confluence? any product?
Where to start?
etc.
ie, ref to Atlassian team doc missing...

[hanna_podoliak]

It broke everything
We had teams created in the plan and now one more was created for each automatically and as a result, we have problems with all filters and automation

[Haddon Fisher]

This is a great step! I can't help but point out thought that this isn't very useful because teams in and of themselves aren't useful. Is there any information on when we will be able to....

• Permission Jira and Confluence using the 'team' object?
• Have a team or multi-team picker custom field in Jira?
• Use a team or multi-team picker in approvals or other logic areas?

[Michael G_]

This doesn't seem available on my organization's teams yet. Has this rolled out to everyone? We're on Jira Software Cloud Premium.

[JG Meillaud _]

Hi,

This is great! (and I assure you, no one outside of Atlassian thought this was a "small inconvenience")

Is it possible to prevent users to create teams?

Thanks,
JG

[Vernon Laquindanum]

Hi @Nathan Allen

Yes, you should be able to use the Team Public REST API to manage teams. You can find the API documentation here.

If there's anything specific you are looking for, please let me know and I can forward to the team if needed.

Hope this helps!

[Nathan Allen]

Thanks Vernon.

This is helpful and I'm really happy to see continued progress towards consolidating the various "Team-like" objects that exist in the Atlassian Universe!

[Vernon Laquindanum]

Hi @Christine Absil

Sorry for the confusion here! Teams are a built-in feature available to use across Confluence Cloud, Jira Software Cloud, Jira Work Management Cloud, Jira Service Management Cloud, Atlas, and Compass.

You can find more information about teams here. Hope this helps!

[Vernon Laquindanum]

Hi @Haddon Fisher

Totally valid points—we're always trying to balance improving core functionality while building out some new features. I can't give exact details, but I can share the following:

• Using teams to enable permissions in Confluence is something we've been discussing and exploring how this could work. One of these steps is the recent addition of membership controls for teams, which makes them more secure by requiring people to request to join or be invited by an existing member.
• We're currently in the process of rolling out the Team custom field in Jira Software Cloud, Jira Service Management Cloud, and Jira Work Management Cloud. We shared recently that Free and Standard user rollout should be complete, with Premium and Enterprise in progress.

We appreciate the honest feedback as always, and hope you find teams more useful over time.

[Vernon Laquindanum]

Hi @hanna_podoliak

I'm so sorry for the late reply, and also to hear things have broken. If the problem is still ongoing, could you share more details on what happened? I can get in touch with the team and see if we can resolve the problems.

[Vernon Laquindanum]

Hi @JG Meillaud _

Glad to hear it! I can't give any specifics, but we are currently working on a way to assign team creation and viewing permissions in Atlassian Admin. We're still exploring the best way to implement these controls, and we hope to have more to share soon.

If you have any other feedback, please don't hesitate to shout out! We're always looking for more ways to improve.

[Vernon Laquindanum]

Hi @Michael G_

Sorry for the late reply—this should be available for all organization admins at this time. If you are an organization admin and don't see the additional controls for teams you're not a part of, please let me know and I can work with the team to investigate further.

[Michael G_]

@Vernon Laquindanum I am a site admin, and when I view a team I am not on then I only see the options to Join or give kudos:

[Haddon Fisher]

Vernon Laquindanum first off, thanks for engaging here! I know community can be a difficult place for Atlassian peeps sometimes but we do it out of love :)

Second, AWESOME news about a team-picker field. Have to ask though...is it going to be usable in all situations and otherwise act like a normal field? This is a problem already (looking at you, user-picker fields in team-managed projects) and frankly I would MUCH rather have these gaps plugged than new functionality added.

Re: permissioning....membership access controls are very good and useful, but at the risk of beating a dead horse this thing right here is probably the most valuable feature around teams so please make sure it remains top of mind.

[Ray Nixon]

It seems like Admin's can't manage (or even see) a team if 1) They are not part of the team, AND 2) The team isn't open for everyone to join. 

This is particular annoying if you (an admin) creates a team with those conditions and then are unable to see it. Why is it not possible for admin's to manage teams they are not a part of, and also not let everyone join those teams? 

[Vova Grebenshchikov]

Still looks like not finished feature -

1. If site admin created non-public team and he is not a memeber - he even cannot edit it any more
     - VERY annoying

2. Team select in JQL is great, but once you saved filter and then edit -> you have zero chances decode GUID back to team name. How filtering done for groups - is much more logical (memberOf)

     - Weren't you ashamed to publish this?:   team[team] = 84f6e838-9649-4c76-b8bf...

3. It is not possible to do JQL queries like "assignee in team(X)"

4. In rules action it is impossible to set team value unless specifying JSON with GUID inside 

so

5. To assembly automation which will set proper team on issue assignment - one need to add team-filters with list of team members (duplicating teams definitions) in order to build rules like:

   if new assigne in team X set issue team to X
   if new assigne in team Y set issue team to Y
...
   - very painful, especialy if you have many teams