Add ability to copy Feature Flag user list to clipboard
Problem to solve
Coming From #14728 (comment 329405576).
After delivering ability to add and remove users to a Feature Flag to expose a feature to only those specified users. The problem is that the current implementation is not scalable for many users, since:
- The users need to be added one by one (via UI)
- Each feature flag needs is independent in the sense that the users to be added to each flag
This makes this use case impractical for customers who wish to add many users to different flags.
Intended users
- 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
Note: The userids listed belong to the 3rd party application and not to gitlab users (with the exclusion of dog-fooding) UserID selection is based on simple string matching, as you can see how it works if you use the Unleash UI here: https://gitlab.com/gitlab-org/gitlab-ee/uploads/c5752845de124863b0d2889b28c9d244/image.png
Further details
Proposal
- We remove the
Edit
button on the userlist list view and make the title of the list link to the userlist detail page. - The
edit
andAdd Users
buttons on the userlist detail page are merged into oneEdit Userlist
button - The new
Edit User List
button links to where the now removed edit button originally linked to (note copy might differ from mockups, please use the copy as defined here). - The modal to add users is removed.
- Leave rest as is (keeping the scope super minimal)
Mockup (browser made) |
---|
Mockup (browser made) |
---|
Loom explanation video |
---|
Link |
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.