• 49
    • 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.

      Current missing capabilities:

      1. Not able to search for Atlassian account ID based on search query such as email address

      There is an API provided by Jira cloud /rest/api/3/groupuserpicker?query=query but the account ID cannot be returned if the account does not have access to the site.

      • Suggestion : Allow to extract Account ID information based on search by email address via the organization rest API: GET /admin/v1/orgs/{orgId}/users/search?query=email_address
      • Workaround : Load the managed accounts data via the GET /admin/v1/orgs/ORG_ID/users/ endpoint and search for the accountID

      2. No way to use Rest APIs to obtain a list of users and their associated sites/products/applications (in order to better audit and manage license consumption, especially for customers on annual billing)

      • Suggestion: Propose that Org REST API include endpoints to include this information, the same way that it is possible to obtain via the Export accounts button, present on Organization > Directory > Managed Accounts

      3. No way to retrieve the license limit and usage.

      • Suggestion : Provide an API that can return the license information and usage per product in each site, Enterprise and Atlassian Access.
      • Suggestion: Provide an API to return distinct users of an enterprise plan per product, the same way that it is possible to obtain via the Export button, present on Organization > Products > User counts > select View on a product

      4. MFA status of users in the organization

      • Workaround: export managed users in the admin page

      5. API endpoint allowing to retrieve organization API keys

      6. Mechanism used to login by the end user i.e. SSO/username+password/OAuth and include if MFA was used to access the cloud app.

      • Workaround: Cumulative percentage is shown for Managed account Secure login. Insight tab shows user count for 2FA and SSO enabled.

            [AX-698] Add capabilities to organization REST API

            Matheus Oliveira (Inactive) added a comment - https://getsupport.atlassian.com/browse/PCS-303067

            jason.rusk added a comment - - edited

            Description:
            Currently, the only way to get "product_access" for each user is to go through the Org API, get the entire list of users in that Org, and then search the paginated data (limit 50 users per page) for the specific user data needed. This can take a long time depending on how big the org is and what software/platform you are using to consolidate and parse the data, vs milliseconds to a single user endpoint.

            Ask: Please create a single user endpoint for the Org API.
            Existing:  https://api.atlassian.com/admin/v1/orgs/orgid/users
            It will give you 50 results and provides the url for the next page. whereby you can get the next set of users:

            Suggestion 1: maybe implement a separate endpoint per user?

            https://api.atlassian.com/admin/v1/orgs/orgid/users/accountId

            Suggestion 2: or a search function with accountId (returns single json object) and email (returns array of of json objects if duplication of email is allowed) as available parameters?

            https://api.atlassian.com/admin/v1/orgs/orgid/users?accountId=accountId

            https://api.atlassian.com/admin/v1/orgs/orgid/users?email=email

             

            It seems a little strange that you can get the list, but not the single user from the Org API.

            jason.rusk added a comment - - edited Description: Currently, the only way to get "product_access" for each user is to go through the Org API, get the entire list of users in that Org, and then search the paginated data (limit 50 users per page) for the specific user data needed. This can take a long time depending on how big the org is and what software/platform you are using to consolidate and parse the data, vs milliseconds to a single user endpoint. Ask: Please create a single user endpoint for the Org API. Existing:  https://api.atlassian.com/admin/v1/orgs/ orgid /users It will give you 50 results and provides the url for the next page. whereby you can get the next set of users: Suggestion 1: maybe implement a separate endpoint per user? https://api.atlassian.com/admin/v1/orgs/ orgid /users/accountId Suggestion 2: or a search function with accountId (returns single json object) and email (returns array of of json objects if duplication of email is allowed) as available parameters? https://api.atlassian.com/admin/v1/orgs/ orgid /users?accountId=accountId https://api.atlassian.com/admin/v1/orgs/ orgid /users?email=email   It seems a little strange that you can get the list, but not the single user from the Org API.

            At my org we are trying to build out automation for Users Access Reviews. One of the things we are facing is we can't automate this with Atlassian Cloud. Manual process can dump this into Sheet or Excel but want this to dump into Sheet for us without human interaction on a quarterly bases with our UAR ticket creation. 
            Open to suggestion with using the current API but not sure how to do this right now. I believe this request would help us complete this task. 

            Aaron Geister added a comment - At my org we are trying to build out automation for Users Access Reviews. One of the things we are facing is we can't automate this with Atlassian Cloud. Manual process can dump this into Sheet or Excel but want this to dump into Sheet for us without human interaction on a quarterly bases with our UAR ticket creation.  Open to suggestion with using the current API but not sure how to do this right now. I believe this request would help us complete this task. 

              2015ae912494 Stefan Scorse
              rmacalinao Ramon M
              Votes:
              37 Vote for this issue
              Watchers:
              52 Start watching this issue

                Created:
                Updated: