This is a reminder for the depreciation of groupname field starting February 28, 2023. We are now in the last month of 6 month deprecation period. We request you to make the necessary changes, if not done already. More details can be found in this post - Adding support for groupID field in Jira REST APIs, expressions types
Hi @Prashanth_M ,
Are you aware of the remaining APIs that don’t yet support groupIds (see comments on the original announcement)? Will they be fixed before you start removing group name support?
Just want to remind again that in order to migrate to the new structure, we need to use one of these endpoints:
GET /rest/api/3/group (Deprecated)
GET /rest/api/3/group/bulk
GET /rest/api/3/group/member
All of them require ADMIN scope and this is a blocker for the migration. The same thing is discussed on various issues and blog posts but there is no response from Atlassian. Don’t you guys see this as a blocker?
We have decided the extend the deadline for the deprecation of Ecosystem APIs which use group-name as an identifier. The decision is based on the concerns raised by the developer community regarding the adoption of group-id. We are committed to completely resolving all concerns raised by our partners. Therefore, we have decided to extend the deadline for Ecosystem API deprecation by 2 months. The new deadline is April 30, 2023 . However, we request the community to continue adopting group-id, so that we can uncover and resolve any new concerns.