"Key" and "Name" are no longer appearing in the User object json in v2 rest api

unknown

Hi,

Our Jira integration is having trouble today. The issue is that our integrations depends on "key" and "name" being set in the User json object when calling this endpoint

https://contrast.atlassian.net/rest/api/2/user/assignable/search?project=10000

The docs indicate the two fields named "key" and "name" will be present in the response

{
  "self": "https://your-domain.atlassian.net/rest/api/2/user?accountId=5b10a2844c20165700ede21g",
  "key": "",
  "accountId": "5b10a2844c20165700ede21g",
  "name": "",
  "emailAddress": "mia@example.com",
  "avatarUrls": {...},
  "displayName": "Mia Krystof",
  "active": true,
  "timeZone": "Australia/Sydney",
  "groups": {
    "size": 3,
    "items": []
  },
  "applicationRoles": {
    "size": 1,
    "items": []
  }
}

Our integration depends on those keys. Sometime on Tuesday (that's when we noticed, anyway), our integrations broke. Inspecting the response, "key" and "name" are no longer present. Here's an example response

 

{        
"self": "https://oururl.atlassian.net/rest/api/2/user?accountId=222222222",        
"accountId": "2222222222",        
"accountType": "atlassian",        
"emailAddress": "",        
"avatarUrls": { ...},        
"displayName": "An Employee",        
"active": true,        
"timeZone": "America/New_York",        
"locale": "en_US"    
}

Was this an intentional change?    We need to act fast to restore service in our integration. If key and name are gone forever, we can change our code to somehow mitigate this. However, if they're coming back and this was a bug, then we can wait until then.

Thanks.

Chirag Shukla

We are seeing a similar issue. Reporter's name is no longer present. There's displayName but no name. We'd like to know whether this is a bug or a permanent thing. If it is a bug, we can wait for it to be resolved. If it is permanent, we will have to rewrite some of our code.

EDIT BELOW

Just came across https://community.atlassian.com/t5/Jira-questions/REST-API-numerous-calls-now-throwing-an-error/qaq-p/1305234. Looks like we'll have to use accountId instead of name.