Skip to content

Clarify Last Activity as Last GitLab Activity on Usage Quotas page

Vamsi Vempati requested to merge clarify-last-activity into master

What does this MR do and why?

Clarify Last Activity as Last GitLab Activity on Seats and Code Suggestions tab on Usage Quotas page.

Related to https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/7834+

Screenshots or screen recordings

Scenario Before After
Seats tab Screenshot_2023-11-15_at_11.15.33_AM Screenshot_2023-11-16_at_10.00.01_AM
Exported member list Screenshot_2023-11-16_at_10.43.28_AM Screenshot_2023-11-16_at_10.42.04_AM
Code Suggestions tab Screenshot_2023-11-15_at_11.15.09_AM Screenshot_2023-11-15_at_10.56.53_AM

How to set up and validate locally

Application setup

  1. Customers Dot needs to be setup in order to view the billing page for a group
  2. Start GDK in SaaS mode GITLAB_SIMULATE_SAAS=1 gdk start

Group setup

  1. Create a Group
  2. Buy a Premium or Ultimate Subscription for your group from Settings > Billing

Feature flag

Run the following in your rails console

Feature.enable(:hamilton_seat_management, Namespace.find(your-group-id)

Add-on purchase

Run the following in your rails console

  1. Find the namespace
namespace = Namespace.find(your-group-id)
  1. Create an Addon
add_on = GitlabSubscriptions::AddOn.find_or_create_by!(name: "code_suggestions") {|e| e.description = "Test"}
  1. Create an add-on purchase
GitlabSubscriptions::AddOnPurchase.create!(add_on: add_on, namespace: namespace, expires_on: 1.month.from_now, quantity: 20, purchase_xid: 'A-S0001')

Seats tab

  1. Go to Settings > Usage Quotas > Seats tab

Code Suggestions tab

  1. Go to Settings > Usage Quotas > Code Suggestions tab

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 Vamsi Vempati

Merge request reports