REST API Create Issue - reporter field passing causing trouble

[RGIRIGOWDA]

Hi,

I went through so many posts suggesting answers, none of them working for me. 

I am calling REST API to create issue, part of it i need to pass Reporter field, in the fields if i pass reporter accountid alone i get success, else all other scenerios i get error. For me email ID is the unique ID i need to use to pass, please help with insight why this is not working. 

"reporter":{"accountId": "5defa1XYZ......."},  --> It works

"reporter":{"emailAddress": "rtest@org.com"}, --> i get "errors": {"reporter": "Reporter is required."}

"reporter":{"name": "firstname lastname"}, --> i get "errors": {"reporter": "Reporter is required."}

"reporter":{"displayName": "firstname lastname"}, --> i get "errors": {"reporter": "Reporter is required."}

[Prince Nyeche · Accepted solution]

Hi @RGIRIGOWDA 

On Atlassian Cloud, accountId is required to identify who the users are. it works on any user picker field e.g. watcher, reporter, assignee etc

Since you're integrating this from another system that uses email ID, you can pass a username parameter to get the accountId using this endpoint for bulk migration (usernames on Cloud is usually the prefix of the email address e.g. max@example.com; username=max). You can look into this idea as that's one of the endpoint to actually get accountId and you can use it elsewhere in your Script.

[Bill Sheboy · Accepted solution]

Hi @RGIRIGOWDA  -- Welcome to the Atlassian Community!

After the GDPR changes, and the deprecation of most of the user-related parameters, it appears you can no longer create an issue without the accountID values for the users involved using the REST API.

https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

https://blog.developer.atlassian.com/creating-a-jira-cloud-issue-in-a-single-rest-call/

Best regards,

Bill