Error- "Reporter is required" With reate Isssue REST API despite mentioning the reporter

[Salesforce Integration]

Im ll in a sudden recieving errors that "reporter is required" on create ISSUE API despite mentioning the correct reporter name .

The automated job was tunning fine until last month. suddently i get this ISSUE , it used to work perfectly back then.

{
"fields": {


"project":
{
"key": "PROD"
},
"summary": "Always do right. This will gratify some people and astonish the REST.",
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"text": "Order entry fails when selecting supplier.",
"type": "text"
}
]
}
]
},
"issuetype": {
"id" : "10000"
},
"reporter" : {
"name" : "Jeff.May"
}
}

}

[Chris Doman]

https://community.atlassian.com/t5/Jira-questions/where-can-i-find-my-Account-ID/qaq-p/976527

https://********.atlassian.net/people/5bb7ad0ccc53fd0760103780

The bold part of the URL is my accountID

[Thomas Deiler]

Dear @Salesforce Integration ,

if it worked before and you didn't change anything in your client rest call, the cause is most probably: The REST API changed.

Its a cloud product that continuously changes. Have a look at the API DOC. In the example they do not use "name" for the reporter but it's ID:

"reporter": {
"id": "5b10a2844c20165700ede21g"
},

So long

Thomas

[Jean-Pierre Caron]

We have the same problem and we are using v2.

Could anyone point to the API DOC and show the expected possible value(s) for reporter (not example) ? 

[Jean-Pierre Caron]

Also, anyone know which receiver list I need to be on to ensure that I know this type of changes ahead of time (and how to test them ahead of time). Cannot play catch up on Jira API once it is actually out there and have tool downtime due to a Jira API issue.

[Thomas Deiler]

Dear @Jean-Pierre Caron ,

its same for V2.

If this not enough, I request you to ask the more detailed developer questions at: https://community.developer.atlassian.com/

So long

Thomas

[Jean-Pierre Caron]

Here is the reason for the change:

https://marketplace.atlassian.com/apps/1219041/gdpr-dsgvo-and-security-for-confluence?hosting=cloud&tab=overview

https://confluence.atlassian.com/jirasoftwarecloud/changes-to-usernames-in-jira-cloud-967319102.html