Not getting reproduced: User value will be null in the issue is the user has removed the visibility

[Nimish Nalan]

In the documentation it is said that:

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

Changes to the visibility of user information: Users will be able to restrict the visibility of their personal data through their user profile privacy settings, or in the case of a managed account, the visibility settings that are decided by the site administrator. This means that fields such as email will only be returned by the API if the user has permitted that data to be visible. Note that this means that some fields can be null. The REST API changes will be introduced alongside the existing REST API. The existing REST API will be available until the end of the deprecation period. Until this time, you can use either the GDPR-compliant or non-GDPR compliant version of the REST API. An opt-in mechanism will be provided for testing at a later stage. This mechanism will force Jira Cloud to only use the GDPR-compliant version of the REST API (that is, deprecated data is not used).

I was not able to reproduce the issue.

I was able to remove the user settings. Through this:

https://confluence.atlassian.com/doc/user-email-visibility-138596.html

But how to reproduce the issue stated above by completing removing the visibility of their personal data through their user profile privacy settings

[Andy Heinzer · Accepted solution]

There is a mismatch between the two documents you cited, but there is a good reason for that:  The first document is a Jira Cloud REST api notice of changes to the platform.   Whereas the 2nd document is specific to the Confluence product and how user accounts are displayed there, not Jira.

This first link is geared towards developers that either create their own plugins, or advanced users that utilize scripts to make changes via the API to Jira Cloud sites.

If you're specifically concerned about hiding user email addresses in Jira, and you are a site-admin member, then there is a setting in the system administration panel that will allow you to control which users can view other users email addresses.   Check out Configuring Jira application options

You will find there is a option there called 'User email visibility' that will allow you to select options such as:

Controls how users' email addresses are displayed in the user profile page.
- PUBLIC - email addresses are visible to all.
- HIDDEN - email addresses are hidden from all users.
- MASKED - the email address is masked (for example, 'user@example.com' is displayed as 'user at example dot com').
- LOGGED IN USERS ONLY - only users logged in to Jira can view the email addresses.

Default: PUBLIC

 I hope this helps.

Andy

[Nimish Nalan]

Hi Andrew,

Even if I do this setting the user is not null in the response(which is specified in the deprecation notice). Only the user email part is hidden. The rest of the user object is present.

Thanks and regards,

Nimish Nalan

This part of the response for the request of getting an issue:
Without the user name hidden:
"creator": {
      "self": "https://IHideThis****/rest/api/2/user?accountId=5b03e4136799f234911212b2",
      "name": "automationsyncuser",
      "key": "automationsyncuser",
      "accountId": "IHideThis****",
      "emailAddress": "automationsyncuser@opshub.com",
      "avatarUrls": {
        "48x48": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=48&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D48%26noRedirect%3Dtrue",
        "24x24": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=24&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D24%26noRedirect%3Dtrue",
        "16x16": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=16&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D16%26noRedirect%3Dtrue",
        "32x32": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D32%26noRedirect%3Dtrue"
      },
      "displayName": "AutomationSyncUser",
      "active": true,
      "timeZone": "America/Los_Angeles"
    },
    
    Making the username as hidden through the settings:
    creator": {
      "self": "https://IHideThis****/rest/api/2/user?accountId=5b03e4136799f234911212b2",
      "name": "automationsyncuser",
      "key": "automationsyncuser",
      "accountId": "IHideThis****",
      "avatarUrls": {
        "48x48": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=48&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D48%26noRedirect%3Dtrue",
        "24x24": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=24&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D24%26noRedirect%3Dtrue",
        "16x16": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=16&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D16%26noRedirect%3Dtrue",
        "32x32": "https://avatar-cdn.atlassian.com/07f358989647af5a38ae88f6480ad97f?s=32&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2F07f358989647af5a38ae88f6480ad97f%3Fd%3Dmm%26s%3D32%26noRedirect%3Dtrue"
      },
      "displayName": "AutomationSyncUser",
      "active": true,
      "timeZone": "America/Los_Angeles"
    },

[Andy Heinzer]

Ah, ok.  I better understand now.  The hiding of the email feature doesn't really apply to what you are wanting to do here.  That is a feature that has existed in Jira for a long time.  However the first link you posted in regards to the deprecation of the API user calls / the ability for users to hide their information.

These changes to the API and user's ability to hide their own user information are still in the process of being rolled out to all of the Jira Cloud sites.  In your case, I would not expect to necessarily see all these changes until the date in the notice: 29 March 2019.  It is possible your Cloud site could gain these new features before that date, but as of today, even my own Jira Cloud instance does not have this ability yet. 

[Nimish Nalan]

Yeah 🙂. Also, is there any documentation which provides the information regarding what will be the response(which contains user object) in the cases where this feature is introduced to Cloud?

Thanks,

Nimish