Issue related to this article: https://community.developer.atlassian.com/t/adding-support-for-groupid-field-in-jira-rest-apis-expressions-types/61045

Using the same syntax for the visibility attribute (i.e. providing identifier with the groupId in place of value with the group name) leads to succeed if we call the endpoint
POST /rest/api/2/issue/{issueIdOrKey}/comment
while we get a 400 error when hitting the endpoint
POST /rest/api/2/issue/{issueIdOrKey}/transition

For the second endpoint to succeed, the value attribute for visibility needs to be present and filled in. The behavior of the API is inconsistent.