Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,938
    • Issues 34,938
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,283
    • Merge Requests 1,283
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #7008

Closed
Open
Opened Jul 24, 2018 by Jeremy Watson@jeremy-gl🤠Maintainer1 of 1 task completed1/1 task

Incorrect Max and overage users due to non-12 month subscription length

Problem to solve

When viewing Maximum Users and Users Over License in /admin, we have a couple of problems:

Primarily: Maximum Users is tied to a fixed 12 month rolling cycle. For some enterprise customers, we do quarterly and semi-annual true-up reviews. While this is OK for the 1st review, subsequent reviews don't work since they may have lowered their utilization - but we're unable to see it, since Maximum Users (and Users Over License) is still reflecting the high watermark from the previous period.

UPDATE 2020-12-01: removing the below portion of the original description for future iteration in #290202:
Secondly, there's no timestamp or date info presented, so we don't have a sense of when a customer went over the limit if they owe a true-up. If we knew which month an instance went over their limit, we could look at users added during that month to give instances a good way to look back on why they went over.

See an explanation of how we are currently calculating Max user count in self-managed here for reference.

Proposal

ORIGINAL PROPOSAL: On the last day of each month, record the instance's 1) maximum number of users for the month, and 2) how many Users Over License they went. Record 0 if they didn't exceed the seats allocated for their license. Present this in the admin panel UI.

CURRENT PROPOSAL: Change the logic to be for the date range applicable to the subscription start and end which is available on the license.

Documentation updates

  • Subscription Faq: https://about.gitlab.com/pricing/licensing-faq/#how-are-maximum-users-calculated

Links / references

Edited Dec 14, 2020 by Jason Goodman
Assignee
Assign to
13.7
Milestone
13.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#7008