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

Jira Development Jira Cloud Announcements
, , , ,
23

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: {"comment": "Group level cannot be empty"}
which means the value attribute (holding the group name) remains mandatory.

Are you going to align the behaviour of this second endpoint to that of the first?
Cheers