Hi April,

When I mention filtering, I mean adding the ability to filter teams by name. It would be great if you could include an optional 'query' parameter, similar to the one used in the projects API: Jira Projects REST API.

The goal is to implement a searchable select on the UI, allowing users to quickly locate specific teams.

Beset wishes!
Volodymyr

Hey cfc20b14a613 ,

Thanks for your response! What do you mean by filtering by name? Can you please share your use case so I can share and discuss this with my team?

Thank you!

Regards,

April

Hey Yong fd37c3375774 ,

Thanks for the response. You should be able to retrieve all Teams albeit it's paginated so you'll need to go the subsequent pages. Does this work for you? Let me know (attach screenshots and error messages if you encounter anything so I can help troubleshoot to the best of my ability)

Regards,

April

Hi April,

Filtering by name is an essential feature. I would greatly appreciate it if you could add this promptly .

Best wishes!
Volodymyr

Hi April,

I have a site with more than 1000 teams, how can I retrieve all the teams then?

I tried both GraphQL and Open API and it seems they can't handle with such big number of teams.

Thanks,

Yong

Hi everyone,

My name is April and I’m a product manager at Atlassian 👋 We’re happy to announce that you can now fetch all your Teams using the REST API. You can start using it today - the documentation is available here.

There are certain asks we're heard from around Public Team APIs:

• Search team by name
• API response to include membership information
• API response to include last updated information

Please let us know if you have any further asks, questions, or suggestions around this. We appreciate your valuable feedback and thank you again for helping us improve the product 🙏

Regards,

April

While this issue still claims to be 'Gathering interest', the GET teams REST API has seemingly been made available meanwhile (works for me):

This returns a list of all teams contained under an organization. This may be used as an option to export teams data within your organization.

Having the ability to query all teams in a Site is a critical feature for integrating with Atlassian Teams, without it how can we be sure we are gathering data on all of our existing teams? This feature seems like it would be quite simple to implement regardless of the implementation. 

Hi f72d1ea2951a ,

If you know the team identifier you can use both the public REST API and the public GraphQL API, as you prefer. Both of them will return the team members. See the links to the documentation in my previous comment.

Regards,

Diego

We have a Jira integration which requires us to determine the team members. Please provide an api to lists members of teams

Hi, this is an update from the Atlassian development team regarding the current situation of the public APIs for teams.

There is a public REST API for teams, which is documented in https://developer.atlassian.com/platform/teams/rest/v1/api-group-teams-public-api/#api-group-teams-public-api . It does support some operations on teams and members, like getting team data, creating teams and adding and removing team members.

The description of this feature request asks for an API to enumerate the teams in an organisation. At this time, we do not have such API, but we continue gathering interest on it and we may introduce it at a later date.

We know that some customers are also interested in a public API to search teams by name. This is not a current capability of the public REST API for teams, but it is already available in the public GraphQL API of Atlassian (api.atlassian.com/graphql). You can find more details about how to use it at https://developer.atlassian.com/platform/teams/teams-graphql-api/introduction/ and navigate the reference documentation using the documentation explorer at https://api.atlassian.com/graphql .

We use teams in Jira Service Management and for basic stuff we need a REST API. i.e. mange the team but also get team members' mail address in automation/via REST to send notifications to a team.

• The team field is used in a manner at some orgs where it becomes critical on how issues are tagged and separated our via area/project.

• The reporting team pulls data from Jira daily as part of an ETL job into their data mart for various purposes including to verify data quality/data integrity and compliance.

• Not having been able to pull this team data from cloud the same way they have been doing from DC through the http://JiraURL/rest/teams-api/1.0/team endpoint is a blocker for them. At the very least, they need to pull the team name and ID and if a team is shareable or not. The fact that it is ‘shareable’ or not (meaning public or private) is a nice to have but not critical but team name and ID are absolutely critical to have.