• 48
    • 19
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, if a user has visibility of email address set to “Only you and admins” in https://id.atlassian.com/manage-profile/profile-and-visibility emailAddress is not returned in REST API responses

      The customer would like the following behaviour

      • When a Jira admin/site admin calls a REST API endpoint returning user information, the API responses should include the emailAddress of users in the responses
      • They would like this to be the case irrespective of the visibility of email address set in https://id.atlassian.com/manage-profile/profile-and-visibility
      • Rationale - Jira admin/site admin are able to see the email address information via the UI and therefore should see the same behaviour when using the REST API.

            [JRACLOUD-80288] emailAddress of users in REST API responses

            Pinned comments

            Pinned by Hala ElRoumy

            Hala ElRoumy added a comment -

            Dear Customers, 

            We have a new update regarding this feature and it can be tracked on this request:

            Thanks,
            Hala | Atlassian Support Team

            Hala ElRoumy added a comment - Dear Customers,   We have a new update regarding this feature and it can be tracked on this request: ID-77744 - Allow site admins to fetch email addresses when using the REST API endpoints to get all users Atlassian Update – 12 April 2024 Hi all, We have a new API available here: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v1-orgs-orgid-users-search-post that returns the user email address regardless of profile visibility setting. Thanks, Stefan Thanks, Hala | Atlassian Support Team

            All comments

            Pinned by Hala ElRoumy

            Hala ElRoumy added a comment -

            Dear Customers, 

            We have a new update regarding this feature and it can be tracked on this request:

            Thanks,
            Hala | Atlassian Support Team

            Hala ElRoumy added a comment - Dear Customers,   We have a new update regarding this feature and it can be tracked on this request: ID-77744 - Allow site admins to fetch email addresses when using the REST API endpoints to get all users Atlassian Update – 12 April 2024 Hi all, We have a new API available here: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v1-orgs-orgid-users-search-post that returns the user email address regardless of profile visibility setting. Thanks, Stefan Thanks, Hala | Atlassian Support Team

            Hi all,

            I'm Eric, a principal developer on the Jira Cloud team.

            I don't anticipate we will ever implement this suggestion as described. In particular we aim to preserve the user's visibility settings.

            2cd38258bd6a, regarding the behaviour of Jira admins not being able to see user email addresses, this is the correct behaviour. Being a Jira Administrator is not sufficient to be able to see a user's personal information if they have not permitted it; users must be Organization Administrators to count as an "admin" for that purpose. I thought I should double check the code though, just in case. I looked just now and it is indeed fetching the email address from the correct place. On rare occasions an empty result will be returned but usually an empty result indicates the caller does not have the user's permission to see their email address.

            982031f333e6 you're correct that there are different APIs for the user admin pages and what is exposed via the Jira REST API. In case you're interested in the internals, these are handled by two different systems and the user management system has a little more knowledge about what is safe to show a given user.

            We are building out APIs that use the user management source and I expect we'll eventually remove the existing Jira APIs (not in the near future and using the standard deprecation process, of course). The organization APIs https://developer.atlassian.com/cloud/admin/organization/rest/intro/#about might be suitable or the user management APIs https://developer.atlassian.com/cloud/admin/user-management/rest/intro/#about for some people's purposes here.

            Eric Dalgliesh added a comment - Hi all, I'm Eric, a principal developer on the Jira Cloud team. I don't anticipate we will ever implement this suggestion as described. In particular we aim to preserve the user's visibility settings. 2cd38258bd6a , regarding the behaviour of Jira admins not being able to see user email addresses, this is the correct behaviour. Being a Jira Administrator is not sufficient to be able to see a user's personal information if they have not permitted it; users must be Organization Administrators to count as an "admin" for that purpose. I thought I should double check the code though, just in case. I looked just now and it is indeed fetching the email address from the correct place. On rare occasions an empty result will be returned but usually an empty result indicates the caller does not have the user's permission to see their email address. 982031f333e6 you're correct that there are different APIs for the user admin pages and what is exposed via the Jira REST API. In case you're interested in the internals, these are handled by two different systems and the user management system has a little more knowledge about what is safe to show a given user. We are building out APIs that use the user management source and I expect we'll eventually remove the existing Jira APIs (not in the near future and using the standard deprecation process, of course). The organization APIs https://developer.atlassian.com/cloud/admin/organization/rest/intro/#about might be suitable or the user management APIs https://developer.atlassian.com/cloud/admin/user-management/rest/intro/#about for some people's purposes here.

            The fact that the admin UI can display these email addresses but I, even using my admin credentials, cannot achieve this through published APIs means that the UI is "cheating" and using methods to access this data that us mere mortals cannot.

            Like NiYunFan, the lack of access to email addresses is breaking our scripts. We only have email addresses as a mechanism to identify users on the platform - we don't and cannot keep track of Atlassian account IDs.

            This should be treated as a bug and not a feature request or an improvement.

            Philip Colmer added a comment - The fact that the admin UI can display these email addresses but I, even using my admin credentials, cannot achieve this through published APIs means that the UI is "cheating" and using methods to access this data that us mere mortals cannot. Like NiYunFan, the lack of access to email addresses is breaking our scripts. We only have email addresses as a mechanism to identify users on the platform - we don't and cannot keep track of Atlassian account IDs. This should be treated as a bug and not a feature request or an improvement.

            NiYunfan added a comment -

            This should be a BUG

            when some user have visibility of email address set to “Only you and admins”, Jira admins can't fetch his email address through REST API

            API for example:  /rest/api/3/group/member?groupname=XXXXXX
            returns a member user without "emailAddress".
             

            We are affected, when using API programming to get and sync Atlassian group members with our HR system (using email address as uniq identity between 2 systems), some users are lost because of missing email address in Jira API response

            NiYunfan added a comment - This should be a BUG when some user have visibility of email address set to “Only you and admins”, Jira admins can't fetch his email address through REST API API for example:  /rest/api/3/group/member?groupname=XXXXXX returns a member user without "emailAddress".   We are affected, when using API programming to get and sync Atlassian group members with our HR system (using email address as uniq identity between 2 systems), some users are lost because of missing email address in Jira API response

              Unassigned Unassigned
              c72c7cdc98e4 Aparna
              Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: