Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-72483

REST API endpoints that return user objects leave email field blank for unmanaged users

      Issue Summary

      Any Jira Cloud REST API endpoint that returns user objects in the JSON response will return a blank email address for any non-managed users. This happens regardless of if they are set to "Public" or "Private" in the Atlassian Account privacy settings (which do not have the email address specific setting for non-managed accounts).

      Steps to Reproduce

      1. Invite an unmanaged user to your instance if one does not already exist
      2. run /rest/api/3/user/search?query=<email address of user>

      Expected Results

      The returned user object email field is populated with the expected email address

      Actual Results

      The email address field is returned with an empty string as the value

      Workaround

      Currently, there is no workaround.

        1. image-2019-07-18-09-37-51-522.png
          19 kB
          Harry J.E Day 🔓 (Last Day 21st July)

            [JRACLOUD-72483] REST API endpoints that return user objects leave email field blank for unmanaged users

            Tj Webb (Inactive) made changes -
            Remote Link Original: This issue links to "HOT-87836 (Atlassian Service Operations JIRA )" [ 438408 ] New: This issue links to "HOT-87836 (Atlassian Service Operations JIRA)" [ 438408 ]
            Veera (Inactive) made changes -
            Description Original: `h3. Issue Summary

            Any Jira Cloud REST API endpoint that returns user objects in the JSON response will return a blank email address for any non-managed users. This happens regardless of if they are set to "Public" or "Private" in the Atlassian Account privacy settings (which do not have the email address specific setting for non-managed accounts).

            h3. Steps to Reproduce
             # Invite an unmanaged user to your instance if one does not already exist
             # run /rest/api/3/user/search?query=<email address of user>

            h3. Expected Results

            The returned user object email field is populated with the expected email address

            h3. Actual Results

            The email address field is returned with an empty string as the value

            h3. Workaround
            Currently, there is no workaround.
            New: h3. Issue Summary

            Any Jira Cloud REST API endpoint that returns user objects in the JSON response will return a blank email address for any non-managed users. This happens regardless of if they are set to "Public" or "Private" in the Atlassian Account privacy settings (which do not have the email address specific setting for non-managed accounts).

            h3. Steps to Reproduce
             # Invite an unmanaged user to your instance if one does not already exist
             # run /rest/api/3/user/search?query=<email address of user>

            h3. Expected Results

            The returned user object email field is populated with the expected email address

            h3. Actual Results

            The email address field is returned with an empty string as the value

            h3. Workaround
            Currently, there is no workaround.
            Jonathan Gan (Inactive) made changes -
            Description Original: h3. Issue Summary

            Any Jira Cloud REST API endpoint that returns user objects in the JSON response will return a blank email address for any non-managed users. This happens regardless of if they are set to "Public" or "Private" in the Atlassian Account privacy settings (which do not have the email address specific setting for non-managed accounts).

            h3. Steps to Reproduce
             # Invite an unmanaged user to your instance if one does not already exist
             # run /rest/api/3/user/search?query=<email address of user>

            h3. Expected Results

            The returned user object email field is populated with the expected email address

            h3. Actual Results

            The email address field is returned with an empty string as the value

            h3. Workaround
            Currently, there is no workaround.
            New: `h3. Issue Summary

            Any Jira Cloud REST API endpoint that returns user objects in the JSON response will return a blank email address for any non-managed users. This happens regardless of if they are set to "Public" or "Private" in the Atlassian Account privacy settings (which do not have the email address specific setting for non-managed accounts).

            h3. Steps to Reproduce
             # Invite an unmanaged user to your instance if one does not already exist
             # run /rest/api/3/user/search?query=<email address of user>

            h3. Expected Results

            The returned user object email field is populated with the expected email address

            h3. Actual Results

            The email address field is returned with an empty string as the value

            h3. Workaround
            Currently, there is no workaround.
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 3299788 ] New: JAC Bug Workflow v3 [ 3362554 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Peter Weinberger made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            SET Analytics Bot made changes -
            UIS Original: 7 New: 6
            SET Analytics Bot made changes -
            UIS Original: 6 New: 7
            Peter Obara made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 442525 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 47 New: 48
            Bugfix Automation Bot made changes -
            Support reference count Original: 46 New: 47

              Unassigned Unassigned
              jlong@atlassian.com Jared Long
              Affected customers:
              31 This affects my team
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: