Skip to content

Migrate project combo selects away from select2

What does this MR do and why?

This migrates the remaining project combo selects to the NewResourceDropdown component. The affected selectors are located in:

  • the instance-level MRs dashboard.
  • the group-level MRs list.
  • the instance-level milestones dashboard.

Screenshots or screen recordings

Note: The REST and GraphQL APIs don't seem to produce the exact same order, hence some discrepancies in the screenshots below. During smoke-testing, it appears that the same entities are available through both versions of the selector even though they might not show up on the initial load 🤔

Before After
Instance-level MRs dashboard Screenshot_2023-01-26_at_8.04.15_AM Screenshot_2023-01-26_at_8.03.38_AM
Group-level MRs list Screenshot_2023-01-26_at_8.05.39_AM Screenshot_2023-01-26_at_8.02.59_AM
Instance-level milestones dashboard Screenshot_2023-01-26_at_8.06.01_AM Screenshot_2023-01-26_at_8.02.31_AM

How to set up and validate locally

  1. Navigate to the instance-level MRs dashboard at /dashboard/merge_requests.
  2. Navigate to a group's MRs list at /groups/:group/-/merge_requests.
  3. Navigate to the instance-level milestones dashboard at /dashboard/milestones.
  4. From each of those pages, you should be able to create an MR or a milestone using the top-right split dropdown.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #374098 (closed)

Edited by Paul Gascou-Vaillancourt

Merge request reports