Hi,
Based on this ISSUE [JRACLOUD-69783] REST API /assignee does not set correctly when using accountId - Create and track feature requests for Atlassian products., it is mentioned that the “id” should be used for accountIds.
But if I’m sending an accountId as ‘id’ with ‘/rest/api/2/issue/{issueKey}/notify’ call then I’m getting an error, the only way it works if I’m explicitly saying ‘accountId’.
So looks like there are inconsistencies across the APIs.
Sample payload:
{
"subject":"subject",
"textBody":"Message",
"htmlBody":"<strong>Message1</strong>",
"to":{
"reporter":false,
"assignee":false,
"watchers":false,
"voters":false,
"users":[
{
"accountId":"557051:113c8625-6eee-4927-b040-67697016c6b1"
}
],
"groups":[
]
}
}
Is this an expected behaviour, or is it going to break in the future?