Deprecation reminder of groupname field in Jira REST APIs

[emre.toptanci]

Hello @Prashanth_M,

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?

Adding support for groupID field in Jira REST APIs, expressions types

G’day @VaradPingale I’ve noticed a non-coherent behaviour between POST /rest/api/2/issue/{issueIdOrKey}/comment and POST /rest/api/2/issue/{issueIdOrKey}/transition The first endpoint allows the following syntax for the attribute visibility: visibility { type: "group", identifier: groupId, }; I.e. we can omit value. When I use the same syntax for the visibility attribute with the second endpoint (in this case inside update.comment[0].add as an example) I get a 400 - Incorrect request…

https://jira.atlassian.com/browse/JRACLOUD-79363