Skip to content

Exposed current_sign_in_at as last login at for billable members

Suraj Tripathi requested to merge issue_370929_add_last_login_at_to_billable_members into master

What does this MR do and why?

Exposes last_login_at in billable_members API

ref: #370929 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Created a group in my local Gitlab env
  2. Added members to the group
  3. Used curl to get the billable members
~ -> curl --header "PRIVATE-TOKEN: <Access key>" "http://localhost:3000/api/v4/groups/<group_id>/billable_members" | jq
[
  {
    "id": 09,
    "username": "suraj",
    "name": "Suraj Tripathi",
    "state": "active",
    "avatar_url": "https://www.gravatar.com/avatar/07bd2091c31509cce650f12ffe48ad8f?s=80&d=identicon",
    "web_url": "http://gdk.test:3000/suraj",
    "email": null,
    "last_activity_on": "2022-10-11",
    "membership_type": "group_member",
    "removable": true,
    "created_at": "2022-04-04T08:33:39.382Z",
    "is_last_owner": true,
    "last_login_at": "2022-10-11 11:49:26"
  }
]

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Suraj Tripathi

Merge request reports