### Problem to solve https://gitlab.com/gitlab-org/gitlab/-/issues/35930 introduced the ability to apply lists as a strategy, but a user could potentially define a large number of lists. This would make the dropdown for selecting the list to apply very long and difficult to use. <!-- What problem do we solve? --> ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> * Developers who create feature flags * QA engineers enabling/disabling flags * Release managers who want to control which features are released and to which customer base * Support engineers that wish to release features to beta customers or test version to fix bugs for specific customers ### Proposal Add the ability to search for a list when selecting a list to apply. ### UX proposal | Desc | Mockup | | ------ | ------ | | Desktop List select list with search |  | | List dropdown loading |  | | List dropdown empty state |  | ### Permissions and Security A user who has permission to the environments referenced in the strategy can modify the strategy settings. <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> * Number of times a list is added/removed to a feature flag * Number of times a user is added/removed to a list ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references