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 | ![]() |
![]() |
Group-level MRs list | ![]() |
![]() |
Instance-level milestones dashboard | ![]() |
![]() |
How to set up and validate locally
- Navigate to the instance-level MRs dashboard at
/dashboard/merge_requests
. - Navigate to a group's MRs list at
/groups/:group/-/merge_requests
. - Navigate to the instance-level milestones dashboard at
/dashboard/milestones
. - 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.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #374098 (closed)
Edited by Paul Gascou-Vaillancourt