Move `seats usage` from billing to usage quotas
What does this MR do?
Closes #334861 (closed)
As part of the long-term vision for Seat Usage documented in &5872 we will move the Seat Usage
page from the current location within Group settings > Billing
directory, to Group settings > Usage Quotas
.
Screenshots or Screencasts (strongly suggested)
Before | After |
---|---|
How to setup and validate locally (strongly suggested)
You need to have a license on your GitLab instance locally in order to enable these views.
Migration of the UI
- Go to Menu > Groups > Your Group
- Chose Settings > Usage Quotas
- You'll see the
Seats usage
UI, with the billable users in "Your Group" - The URL should be
/groups/<your group>/-/usage_quotas#seats-quota-tab
Back end redirection
- If you place this path on your browser:
/groups/<your group>/-/seat_usage
- You should be redirected to
/groups/<your group>/-/usage_quotas#seats-quota-tab
Migration of the link
- Go to Menu > Groups > Your Group
- Chose Settings > Billing
- Under "Seats currently in use" click in the button
Seat usage
- You should be redirected to
/groups/<your group>/-/usage_quotas#seats-quota-tab
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Sheldon Led