Names of Groups no longer immutable after March 27, 2022

What is changing?

Confluence Cloud is moving away from groupName towards groupId as the unique identifier for Groups . See Updates to Group REST APIs and Group Webhook Events for more details and Get Groups API enhanced to support group lookups based on access type for new APIs to get groups based on their roles.

Confluence Cloud is officially starting the 6 month deprecation period. At the end of the 6 months deprecation period, ie, Mar 27, 2022, groupNames will no longer be immutable.

What do I need to do?

  1. Determine if your team is impacted and needs to make the switch to use the new field groupId instead of groupName .
  2. Make the changes in the next 6 months.

By when do I need to do it?

Mar 27, 2022

REST APIs with groupName will still be available for use but groupName will no longer be immutable after this date.

4 Likes

is this planned for Jira Cloud as well?

2 Likes

Very good question. Right now there doesn’t seem to be a concept of groupId in Jira.

Also, if group name is no longer immutable, do the connect conditions that are currently based upon group names also magically start working with groupIds too?? — I think there may be a Jira issue for that somewhere.

I have seen groupId in some Jira Rest Endpoints recently and wondered, that it does not exist consistently in all REST Endpoints … So something might already going on on behind the scenes :slight_smile: