Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #54947
Closed
Open
Created Dec 06, 2018 by Jeremy Watson (ex-GitLab)@jeremy-glContributor

Update last_activity_on on browsing activity

Problem to solve

Instance admins frequently want to answer the question of "when was the last time a user used GitLab?" This is typically asked around true-up time or whenever an admin wants to groom out users who are no longer using GitLab at their organization.

The most common attributes for understanding this are last_activity_on and current_sign_in_at. They both have their drawbacks:

  • last_activity_on updates on events but does not include logins or browsing activity.
  • current_sign_in_at updates on a user logging into the UI, but does not include SSH activity and only updates on the login screen - if the client is logged in with a cookie, this does not update (despite the user using GitLab).

We should have one canonical source of truth for user activity, which should include a user logging into the UI and browsing around.

Proposal

  • last_activity_on should include user browsing activity.

Links / references

Edited Mar 28, 2019 by Jeremy Watson (ex-GitLab)
Assignee
Assign to
Time tracking