Uploaded image for project: 'Admin Experience'
  1. Admin Experience
  2. AX-673

Include 'Last Active Date' as a field in REST API endpoint /rest/api/2/user

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

      N/A

            [AX-673] Include 'Last Active Date' as a field in REST API endpoint /rest/api/2/user

            Rodrigo B. made changes -
            Component/s Original: Admin API tokens/keys [ 54490 ]
            Component/s New: Org Management - Cloud Admin API keys [ 80136 ]
            Key Original: ACCESS-1291 New: AX-673
            Support reference count Original: 58
            Description Original: {panel:title=Atlassian Update – 16 March 2023|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
            Hi all,

            We decided to build a new API to solve this use case you can find it here: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-orgs-orgid-directory-users-accountid-last-active-dates-get

            If you have any feedback regarding the API please reach out!

            Thanks,
            Stefan
            {panel}

            {panel:title=Atlassian Update – 22 July 2019|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
            Hi everyone,

            I have some good news! My team has released a last_active field for managed accounts in the [Organization API|https://developer.atlassian.com/cloud/admin/organization/rest/]. The get users in an org [endpoint|https://developer.atlassian.com/cloud/admin/organization/rest/#api-orgs-orgId-users-get] provides further documentation of this process.

            This API will provide last active date information for managed accounts, which means you must have an organization and a verified domain. An "organization" is a unified view of the sites and products that your company is using. You can check if you have an organization already by visiting [admin.atlassian.com|http://admin.atlassian.com/]. You should see a list of your organizations under "Organizations."

            If you don't have an organization, you can create one by following the directions on [this doc|https://confluence.atlassian.com/cloud/set-up-an-atlassian-organization-938859734.html].

            Once you have an organization created, you'll need to claim a domain, which can be done by following the instructions [here|https://confluence.atlassian.com/cloud/verify-a-domain-for-your-organization-873871234.html].

            After claiming a domain, you should be able to follow the directions on the Organization API [documentation|https://developer.atlassian.com/cloud/admin/organization/rest/] to get last_active data for your managed accounts.

            I hope this is helpful. Please let me know if these directions are unclear or if any additional questions arrive. Thank you for voting and commenting on this issue, and we remain committed to improving the functionality of our REST APIs.

            Thanks,
             Rak Garg
             [rgarg@atlassian.com|mailto:rgarg@atlassian.com]
             Product Manager, Atlassian
            {panel}

             
            h3. Problem Definition

            With the introduction of [Per User Pricing for Atlassian Cloud - Atlassian|https://www.atlassian.com/licensing/cloud/future-pricing] Automating tracking for last active users is important for our Customers to manage and audit their users and to check the accuracy of the billing from Atlassian.
            h3. Suggested Solution

            Add the Last Active Date as a field in the REST API endpoint /rest/api/2/user
            h3. Workaround

            No Workaround for automation, to get the Last Active Date customers are referring to the information in User Management.
            New: N/A
            Project Original: Atlassian Guard [ 18910 ] New: Admin Experience [ 24210 ]
            SET Analytics Bot made changes -
            Support reference count Original: 57 New: 58
            SET Analytics Bot made changes -
            Support reference count Original: 56 New: 57
            SET Analytics Bot made changes -
            Support reference count Original: 55 New: 56
            SET Analytics Bot made changes -
            Support reference count Original: 33 New: 55
            SET Analytics Bot made changes -
            Support reference count Original: 32 New: 33
            SET Analytics Bot made changes -
            Support reference count Original: 30 New: 32
            SET Analytics Bot made changes -
            Support reference count Original: 28 New: 30
            SET Analytics Bot made changes -
            Support reference count Original: 27 New: 28
            SET Analytics Bot made changes -
            Support reference count Original: 26 New: 27

              2015ae912494 Stefan Scorse
              nmuhi Nazri Muhi (Inactive)
              Votes:
              91 Vote for this issue
              Watchers:
              73 Start watching this issue

                Created:
                Updated: