Customers are unable to tell when the max_seats_used was updated for their namespace
Problem
Follow up from support shadowing: https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/694
While working on a ticket we received from a Customer asking about the seat overages for the namespace, it was very difficult to identify the date/event that caused the overage. It was mentioned that sometimes support has to count the membership change events in the group's activity to identify when the overage occurred.
Our GitlabSubscription
table in the GitLab application started storing the value max_seats_used_changed_at
several months ago so we actually have some useful information around this which could help narrow down changes.
Proposal
Display max_seats_used_changed_at
in the UI - either just in CustomersDot for Admin, or even on the Billing page so we can refer back to this with the customer.
Potentially something like this:
Result
It's easier to narrow down the event that caused a seat overage as we'll know what date the max_seats_used
increased.