Skip to content

Add pagination to organization groups list

What does this MR do and why?

Related to #420777 (closed)

The grouptenant scale team is starting to build out an Organization MVC. For more information about what an "Organization" will be see https://docs.gitlab.com/ee/architecture/blueprints/organization/

In !142614 (merged) we swapped a mock GraphQL query for the real one but opted to add pagination in a follow-up MR. This MR adds the pagination to the organization groups list.

Notes for reviewer

  • To keep the MRs smaller search and sorting will be implemented in a separate MR after this is merged
  • The API does not yet support the access level that the current user has so the role badge will not yet be shown. That will be shown after implementing #437683 (closed)
  • Mock data is now only used for specs, we are planning on moving to frontend fixtures in #439147 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screen_Recording_2024-01-28_at_8.31.28_PM

How to set up and validate locally

  1. Open Rails console
    • bin/rails console
  2. Enable the feature flag
    • Feature.enable(:ui_for_organizations)
  3. Navigate to /-/organizations/default, choose Frequently visited groups from the dropdown.
  4. Click View all
  5. If you have less than 20 groups you can set app/assets/javascripts/api.js#L6 to a lower number to force pagination.
Edited by Peter Hegman

Merge request reports