Currently, I am able to add any email(not just jira accounts) as a participant into a service desk task in the UI - works as expected in all ways.
It seems that internally it uses this endpoint:
/rest/servicedesk/1/customer/participants/{issueIdOrKey}/add with a PUT method and this body:
{"accountIds":[],"organisationIds":[],"emails":["testing@example.com"]}... but I was not able to find a documentation for this one - I only found service-desk docs all pretty similar to this one:
https://docs.atlassian.com/jira-servicedesk/REST/3.8.2/#servicedeskapi/request/{issueIdOrKey}/participant-addRequestParticipants
which only mentions "usernames"
and this seemingly newer version of some cloud API docs (which I'm guessing are the right ones for servicedesk hosted on example.atlassian.net?):
https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-participant-post
which mentions "usernames" as being deprecated and that the new way should be "accountIds" - but I certainly do NOT want to create a JIRA/service desk account for each email I am adding to the task as a participant which is solely only for the reason of getting them email copies on status changes...
So my question(s) are:
Which one of these 2 documented endpoints are able to add just an email (without pre-creating account) as a participant to a service-desk task?
If some of them are - how please?
Or do I have to rely on the undocumented customer endpoint? or is it documented somewhere I wasn't ale to find?
And I will emphasize once more - I do NOT want to create an account for each email being added this way that would completely defeat the purpose of this question O:-)
Pretty please and thank you very much ahead :-)
