Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1291

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

XMLWordPrintable

    • 57

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

      Atlassian Update – 16 March 2023

      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

      Atlassian Update – 22 July 2019

      Hi everyone,

      I have some good news! My team has released a last_active field for managed accounts in the Organization API. The get users in an org endpoint 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. 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.

      Once you have an organization created, you'll need to claim a domain, which can be done by following the instructions here.

      After claiming a domain, you should be able to follow the directions on the Organization API documentation 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
      Product Manager, Atlassian

       

      Problem Definition

      With the introduction of Per User Pricing for Atlassian Cloud - Atlassian 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.

      Suggested Solution

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

      Workaround

      No Workaround for automation, to get the Last Active Date customers are referring to the information in User Management.

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

            Ana París added a comment -

            Hi, 

            Do you have an estimated date for when the development will be in production?

            Best Regards, 

            Ana

            Ana París added a comment - Hi,  Do you have an estimated date for when the development will be in production? Best Regards,  Ana

            Dan W added a comment -

            I just ran the api to get the last active dates.  Is is supposed to return all applications?  When I run it I am only seeing Jira and JSM.  Confluence, Trello and Atlas are not included.  Also not seeing the date added to org.  Good start though.

            Dan W added a comment - I just ran the api to get the last active dates.  Is is supposed to return all applications?  When I run it I am only seeing Jira and JSM.  Confluence, Trello and Atlas are not included.  Also not seeing the date added to org.  Good start though.

            Stefan Scorse added a comment -

            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
            Please note that this API is in Beta. 

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

            Thanks

            Stefan Scorse added a comment - 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 Please note that this API is in Beta.  If you have any feedback regarding the API please reach out! Thanks

            周鹏飞 Luka added a comment -

            I also encountered the same problem, very confused

            周鹏飞 Luka added a comment - I also encountered the same problem, very confused

            Deleted Account (Inactive) added a comment - - edited

            Is this api giving the "last_active" based on user activity across Atlassian Products(Jira, Confluence etc) or its on Individual basis ? 

            And if it is not on individual basis then how we can get it per Atlassian product.

            Is there any api available which can tell us about the last_active time across different products ?

            Deleted Account (Inactive) added a comment - - edited Is this api giving the "last_active" based on user activity across Atlassian Products(Jira, Confluence etc) or its on Individual basis ?  And if it is not on individual basis then how we can get it per Atlassian product. Is there any api available which can tell us about the last_active time across different products ?

            Barrett Smith added a comment -

            As a Jira cloud customer, a) with both internal and external users in our organization, and b) who is billed on a per-user basis, I want a means to deactivate users who have not been active in some configurable period of time, so that I can reduce wasted expense.

            This can be done manually at present by,

            a) logging in to the admin interface and clicking through each page of users looking at their last active date in the UI and deactivating them,

            b) logging in to the admin interface and downloading a CSV of all users and scripting calls to deactive the user

            The manual nature of this process adds toil and organizational expense to administering Jira for a large organization with a dynamic membership. Further, as a Jira administrator and a developer, it is incredibly frustrating that I can see the information I need in Jira's UI but am unable to access it through the API.

             

            Barrett Smith added a comment - As a Jira cloud customer, a) with both internal and external users in our organization, and b) who is billed on a per-user basis, I want a means to deactivate users who have not been active in some configurable period of time, so that I can reduce wasted expense. This can be done manually at present by, a) logging in to the admin interface and clicking through each page of users looking at their last active date in the UI and deactivating them, b) logging in to the admin interface and downloading a CSV of all users and scripting calls to deactive the user The manual nature of this process adds toil and organizational expense to administering Jira for a large organization with a dynamic membership. Further, as a Jira administrator and a developer, it is incredibly frustrating that I can see the information I need in Jira's UI but am unable to access it through the API.  

            Joe Sapinoso added a comment -

            Hello, another question I have is that only some of the users listed have a "Last Active" property while some do not. What does this mean?

            Joe Sapinoso added a comment - Hello, another question I have is that only some of the users listed have a "Last Active" property while some do not. What does this mean?

            Joe Sapinoso added a comment - - edited

            Deleted

            Joe Sapinoso added a comment - - edited Deleted

            Dave Meyer added a comment -

            Hi jeremy.treague,

            Apologies for the confusion. Creating an organization, claiming a domain, and managing accounts (and the REST APIs described here) are free to all customers. Atlassian Access is a paid subscription for your organization that includes additional features, but the API rgarg@atlassian.com described is available without additional costs.

            Regards,
            Dave

            Dave Meyer added a comment - Hi jeremy.treague , Apologies for the confusion. Creating an organization, claiming a domain, and managing accounts (and the REST APIs described here) are free to all customers. Atlassian Access is a paid subscription for your organization that includes additional features, but the API rgarg@atlassian.com described is available without additional costs. Regards, Dave

            Jeremy Treague added a comment -

            Hi Rak,

            Thanks for this update and for adding visibility to the "last active" information via the REST APIs.

            In the documentation you referenced (this doc) it notes that administrators who haven't already created an organization can do so using  Atlassian Access.  Does doing so require subscribing to that service, in addition to other services that customers are using from Atlassian (e.g. Jira Cloud Service in my company's case)?   Are there additional subscription costs associated with doing so?

            Jeremy Treague added a comment - Hi Rak, Thanks for this update and for adding visibility to the "last active" information via the REST APIs. In the documentation you referenced ( this doc ) it notes that administrators who haven't already created an organization can do so using  Atlassian Access.  Does doing so require subscribing to that service, in addition to other services that customers are using from Atlassian (e.g. Jira Cloud Service in my company's case)?   Are there additional subscription costs associated with doing so?

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

                Created:
                Updated: