Can confirm that as of now one cannot change the display name of Teams yet (or connect to existing teams, which is planned for later). Generally this all goes in a nice direction though!
@Jared Schmitt Atlassian to confirm but I highly doubt the functionality would be turned off again.
See the post that some features you're asking for might still show during the EAP (see quote below).
non-SCIM group to team mapping - Currently not (see below).
Changing the group name on our IdP doesn't change it on Atlassian side (hence no rename on the Team either), not sure your IdP does handle this differently or it's an Atlassian thing. Definitely something to check.
If we've switched from SCIM to Azure AD for nested groups, is this functionality unavailable to us?
Does this synchronization allow us to BLOCK users from creating their own teams? Or at least teams with the same name (which is inexplicably currently allowed?)
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Are there any plans to further integrate Teams with Assets?
Currently we can only create Assets Attributes for Users and Groups. Now that Groups can be directly connected to Teams, it would be useful to have a Team attribute type.
In case you missed it, you can now connect to existing teams, let me know when you've had a go at it. More updates here.
Changing the group name on our IdP doesn't change it on Atlassian side (hence no rename on the Team either), not sure your IdP does handle this differently or it's an Atlassian thing. Definitely something to check.
This one, I've passed this feedback onto the relevant team. Will get back to you on whether this is something on their radar.
This is on our radar, it's too early to tell what this would look like and what the solution is but highlighting that this is something we're currently looking at and we will have more news on this next year.
Quite sure this stays, worst case the teams would stay and stop being synced but that would only be if something goes drastically wrong I think.
Not sure what the context of this is but as long as you keep having at least 1 premium or enterprise license in Jira, Confluence, Compass, or Loom, you will keep having Managed Teams.
Let me know if you have any other questions or feedback!
- Is this compatible with Azure AD for nested groups? If we've switched from SCIM to Azure AD for nested groups, is this functionality unavailable to us?
I believe this would still work. As long as there's an Atlassian group to exists, you can connect a Managed Team to it. The
In this case, the Azure AD group gets flattened and you should be able to connect your teamsto these groups. Let me know if this isn't the case.
Does this synchronization allow us to BLOCK users from creating their own teams? Or at least teams with the same name (which is inexplicably currently allowed?)
- It doesn't block end users from creating their own teams but in the case of Managed Teams i.e. teams with a tick indicator, noone else to create these teams other than the org admin. This means you can take this as the team is 'good' and 'verified' by admin.
- You can still create teams with the same name unfortunately but you'd be able to distinguish the correct team as it should have a blue tick.
Yes! Thank you for your interest. We're still assessing and adding more EAP customers on a rolling basis. Have you filled out this Google Form yet? https://forms.gle/yGL4XMqLLaV2qXcp8
Hope you're well and thank you for the question as always 🙏
Another bonus question:
Are there any plans to further integrate Teams with Assets?
Currently we can only create Assets Attributes for Users and Groups. Now that Groups can be directly connected to Teams, it would be useful to have a Team attribute type.
Our vision and what we're working towards is that all products should have a single Atlassian Teams concept in the future, so we acknowledge that JSM Assets should integrate with Teams eventually.
Unfortunately, this is not planned yet and isn't on our radar for at least the next 2 years. Reason for this is we're focussing on adding more admin controls to Teams first. I'd be interested in hearing about how you use JSM Assets though and how Teams could fit into this.
I'll be reaching out about calls to speak about the EAP soon, would be great to catch up and see how you're going and touch bases on your use cases for JSM assets too.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Are there any plans to further integrate Teams with Assets?
Currently we can only create Assets Attributes for Users and Groups. Now that Groups can be directly connected to Teams, it would be useful to have a Team attribute type.
Our vision and what we're working towards is that all products should have a single Atlassian Teams concept in the future, so we acknowledge that JSM Assets should integrate with Teams eventually.
Unfortunately, this is not planned yet and isn't on our radar for at least the next 2 years. Reason for this is we're focussing on adding more admin controls to Teams first. I'd be interested in hearing about how you use JSM Assets though and how Teams could fit into this.
I'll be reaching out about calls to speak about the EAP soon, would be great to catch up and see how you're going and touch bases on your use cases for JSM assets too.
Let me know if you'd be interested!
The short version is that in some cases an Assets Object is better connected to a Team rather than an individual User. Let's say you have your internal services or systems as Assets Objects. These could have an Attribute for "Supporting Team".
I am very interested in participating in a call :)
37 comments