Conditionally expose member's is using seat info
What does this MR do and why?
Relates to #459041 (closed), with this MR we're introducing a type: ops FF to conditionally expose using_seat info. More details on why this change and the customer impact can be found on the Issue.
Note that, type: ops FFs, do not require Rollout Issues: Rollout issue: Likely no need for a rollout issues, as it is hard to predict when they are enabled or disabled.
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
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Make sure to have a Namespace w/ a paid subscription
- Copy the namespace ID
- In rails console enable the experiment fully
Feature.enable(:avoid_exposing_member_is_using_seat, <your-namespace-id>) - Visit any group member pages such as
http://127.0.0.1:3000/groups/<your-namespace-name>/-/group_members
Edited by Angelo Gulina