July 5 2019 Change to Webhook User Shape

[Sol Walters]

We have a webhook which we are in the process of updating, and we came across an unusual discrepancy in our webhook logs.

Up to and including July 4, 2019, the shape of the "user" field in what is sent to the webhook looked like this:

"user": {
  "self": "url",
  "name": "name",
  "key": "key",
  "accountId": "id",
  "emailAddress": "address",
  "avatarUrls": {
    "48x48": "url",
    "24x24": "url",
    "16x16": "url",
    "32x32": "url"
  },
  "displayName": "Name of Display",
  "active": true,
  "timeZone": "Timezone",
  "accountType": "atlassian"
},

As of July 5, 2019, the shape now looks like this:

"user": 
  "UserJsonBean{
    self=url, 
    name=null, 
    key=null, 
    accountId=id, 
    emailAddress=\"?\", 
    avatarUrls={
      48x48=url, 
      24x24=url, 
      16x16=url, 
      32x32=url
    }, 
    displayName=Name, active=true, timeZone=Timezone
  }",

My research seems to point to the fact that this is GDPR related, but I could not find any explicit reference to this change in https://confluence.atlassian.com/cloud/blog/2019/07/atlassian-cloud-changes-jul-1-to-jul-8-2019

We can update our hooks on our end to properly address the new changes, but my concern is should we expect further changes to the v2 api/webhooks to be deployed without announcement? Is the UserJsonBean structure the planned structure going forward, or was this a missed wrapper class that wasn't properly sanitized by mistake?

Basically, if we are using webhooks to integrate our workflow on our own systems, can we expect more sudden, undocumented, unannounced changes like this? Or is this a one-off situation due to GDPR and user identification? Or is it a mistake in general?

As a secondary question, the "user" field is what we are using to track the user who triggered the action. As our site is internal, and all of our users who could trigger the action have emails @our-domain.com, we were using emailAddress to connect from the atlassian account to our internal one, but it looks like this change also blasted away the email address. What should I use instead?

[Dario B]

Hi @Sol Walters ,

I can see you already got an answer to this question in a Support Request. However, I am adding an answer to this thread as well as adding more information so that it can be useful to other people searching the community for similar issues.

The behavior you are reporting is related to the introduction of the new Profile and Visibility settings:

• Update your profile and visibility settings

This change was needed in order to comply with GDPR and, as a result, you can or cannot see  user emails depending on how they configured  their profile visibility settings.

Guidelines for developers are available in the below threads:

• Guidelines for Testing Profile Visibility Controls
• Guidelines for requesting access to email address

For any further question on this topic please either ask in the Developer Community or raise  a request with our Developer Support team.

Cheers,
Dario