Username removed from webhook payloads?

[Dane Powell]

I see it mentioned several places that user details were removed from various Bitbucket API and services as of 29 April 2019: https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/

However, I have several Bitbucket-integrated services that I think were still receiving a "username" via webhook payloads up until very recently. 

Did something change recently (in the last few weeks or so) that would have caused the username to be removed? Or would this perhaps vary on an account-by-account basis, such as if the account is subject to GDPR?

[Dane Powell · Accepted solution]

Ah, nevermind, I think I figured it out.

The username reference was a red herring due to a typo in our integration, it's really referring to display_name.

The root issue is that display_name can be an empty string, unlike username before it. The bug on our end was triggered when we encountered a blank display_name for the first time.

And that might not even be related, because we suspect the reason the display_name was empty is because there was no user object due to an incorrect Git username/email address.